Triple
T37845801
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | History of Thailand |
E943595
|
entity |
| Predicate | languageFamilyHistory |
P203648
|
FINISHED |
| Object | Tai–Kadai migrations |
E47577
|
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: Tai–Kadai migrations | Statement: [History of Thailand, languageFamilyHistory, Tai–Kadai migrations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageFamilyHistory Context triple: [History of Thailand, languageFamilyHistory, Tai–Kadai migrations]
-
A.
languageFamilyBranchOf
Indicates that one language family branch is a sub-group or subdivision within a larger language family.
-
B.
basedOnLanguageFamily
Indicates that one entity is derived from, structured according to, or otherwise determined by the language family to which another entity belongs.
-
C.
languageFamilyOfRulers
Indicates the language family historically associated with the rulers of a given political entity or territory.
-
D.
languageFamily
Indicates that two or more languages belong to the same genealogical language family or linguistic lineage.
-
E.
ancientLanguageFamily
Indicates that one language belongs to or descends from a historically ancient family of related languages.
- 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_69f76eeb0f7081908d6d3adbc469889c |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a01bcd39760819081807a02eb1939d1 |
completed | May 11, 2026, 11:26 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a40fb8fd16081908d3f4769fef0d876 |
completed | June 28, 2026, 10:46 a.m. |
| PD | Predicate disambiguation | batch_6a01bc3f1c74819087580e3134affc60 |
completed | May 11, 2026, 11:23 a.m. |
| PDg | Predicate description generation | batch_6a01bcd2d41081909176545b95bba88d |
completed | May 11, 2026, 11:26 a.m. |
Created at: May 3, 2026, 4:19 p.m.