Triple
T13428762
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tai |
E313551
|
entity |
| Predicate | hasMemberLanguage |
P7390
|
FINISHED |
| Object | Bouyei |
E893914
|
NE FINISHED |
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: Bouyei | Statement: [Tai, hasMemberLanguage, Bouyei]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bouyei Context triple: [Tai, hasMemberLanguage, Bouyei]
-
A.
Bouyi
chosen
Bouyi is an alternate name for the Bouyei language, a Tai–Kadai language spoken primarily by the Bouyei ethnic group in southern China.
-
B.
Osanobua
Osanobua is the supreme creator god and central deity in the traditional religion and cosmology of the Edo people of Nigeria.
-
C.
Chō
Chō is a Japanese surname borne by various notable individuals across fields such as the military, arts, and entertainment.
-
D.
Hoan-ya
Hoan-ya is an alternative name for the Hoanya language, an indigenous Formosan language historically spoken in Taiwan.
-
E.
Nishiizu
Nishiizu is a coastal town in Shizuoka Prefecture, Japan, known for its rugged seaside scenery, hot springs, and views of Suruga Bay.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d806ad0c44819088833ae1ec9e9690 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaed304ac8190a8021f749de8164c |
completed | April 12, 2026, 2:40 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f730883cb48190add9469c48dc3e89 |
completed | May 3, 2026, 11:24 a.m. |
Created at: April 9, 2026, 9:40 p.m.