Triple
T9667557
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Li language |
E233743
|
entity |
| Predicate | hasDialect |
P4251
|
FINISHED |
| Object |
Run dialect
Run dialect is a regional spoken variety of the Li language used by the Li people of Hainan, China.
|
E813014
|
NE FINISHED |
How this triple was built (4 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Run dialect | Statement: [Li language, hasDialect, Run dialect]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Run dialect Context triple: [Li language, hasDialect, Run dialect]
-
A.
Vo dialect
The Vo dialect is a regional variety of the Wa language spoken by Wa communities in parts of Southeast Asia.
-
B.
Bzyb dialect
The Bzyb dialect is a regional variety of the Abkhaz language traditionally spoken in the Bzyb River area of Abkhazia.
-
C.
Saga dialect
The Saga dialect is a regional variety of Japanese spoken in Saga Prefecture on Kyushu, known for its distinctive intonation, vocabulary, and grammatical features within the broader Kyushu dialect group.
-
D.
Nzaman dialect
The Nzaman dialect is a regional linguistic variety of the Nzaman language spoken by a specific community, distinguished by its own phonological and lexical features.
-
E.
Abzhywa dialect
The Abzhywa dialect is a major regional variety of the Abkhaz language, traditionally spoken in the Abzhywa (Abzhua) area of Abkhazia.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Run dialect Triple: [Li language, hasDialect, Run dialect]
Generated description
Run dialect is a regional spoken variety of the Li language used by the Li people of Hainan, China.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Run dialect Target entity description: Run dialect is a regional spoken variety of the Li language used by the Li people of Hainan, China.
-
A.
Vo dialect
The Vo dialect is a regional variety of the Wa language spoken by Wa communities in parts of Southeast Asia.
-
B.
Bzyb dialect
The Bzyb dialect is a regional variety of the Abkhaz language traditionally spoken in the Bzyb River area of Abkhazia.
-
C.
Saga dialect
The Saga dialect is a regional variety of Japanese spoken in Saga Prefecture on Kyushu, known for its distinctive intonation, vocabulary, and grammatical features within the broader Kyushu dialect group.
-
D.
Nzaman dialect
The Nzaman dialect is a regional linguistic variety of the Nzaman language spoken by a specific community, distinguished by its own phonological and lexical features.
-
E.
Abzhywa dialect
The Abzhywa dialect is a major regional variety of the Abkhaz language, traditionally spoken in the Abzhywa (Abzhua) area of Abkhazia.
- F. None of above. chosen
Provenance (5 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69ca848d3b6c8190ae98ea554dea58df |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9c3c06e4819080c1b8e66faa482f |
completed | April 1, 2026, 10:29 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d18a208798819088db055e44d288e3 |
completed | April 4, 2026, 10:01 p.m. |
| NEDg | Description generation | batch_69d18ab1239c8190b4a66ccd0db35ffb |
completed | April 4, 2026, 10:03 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69d18b7f7510819083a402d6802c7d95 |
completed | April 4, 2026, 10:06 p.m. |
Created at: March 30, 2026, 8:15 p.m.