Triple
T35905027
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ᦅᧄᦺᦑᦟᦹᧉ |
E1038448
|
entity |
| Predicate | usedBySpeakersOf |
P40748
|
FINISHED |
| Object | Tai Lue language |
—
|
NE NERFINISHED |
How this triple was built (2 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: Tai Lue language | Statement: [ᦅᧄᦺᦑᦟᦹᧉ, usedBySpeakersOf, Tai Lue language]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedBySpeakersOf Context triple: [ᦅᧄᦺᦑᦟᦹᧉ, usedBySpeakersOf, Tai Lue language]
-
A.
usedBySpeakers
chosen
Indicates that something (such as a resource, tool, or method) is employed or utilized by speakers.
-
B.
hasSpeakersAmong
Indicates that a group, event, or entity includes one or more speakers drawn from a specified set or category.
-
C.
representedBySpeaker
Indicates that something is expressed, conveyed, or symbolized through a particular speaker as its representative voice or agent.
-
D.
hasSpeakersIn
Indicates that an entity (such as an event, conference, or session) includes or is associated with speakers located in or belonging to a specified place or group.
-
E.
succeededAsSpeakerBy
Indicates that one entity took over the role or position of speaker from another entity as their successor.
- F. None of above.
Provenance (3 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_69f76e2259608190bf6788a132e0d139 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd5bf69acc819092a01e4259785dc3 |
completed | May 8, 2026, 3:43 a.m. |
| PD | Predicate disambiguation | batch_69fd59b3f4ac8190a7f9dd3142da6e09 |
completed | May 8, 2026, 3:34 a.m. |
Created at: May 3, 2026, 4:07 p.m.