Triple
T27101851
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sonowal Kachari |
E686461
|
entity |
| Predicate | ethnicFamily |
P51397
|
FINISHED |
| Object | Bodo–Kachari peoples |
—
|
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: Bodo–Kachari peoples | Statement: [Sonowal Kachari, ethnicFamily, Bodo–Kachari peoples]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ethnicFamily Context triple: [Sonowal Kachari, ethnicFamily, Bodo–Kachari peoples]
-
A.
mainFamilyEthnicity
Indicates the primary ethnic background or heritage associated with a person’s family.
-
B.
ethnicGroupInFocus
Indicates that a particular ethnic group is the primary subject or focal point within a given context, relation, or description.
-
C.
globalFamily
Indicates a familial or kinship relationship that extends across national or geographic boundaries, connecting family members living in different parts of the world.
-
D.
ethnonymLanguageFamily
Indicates a relationship where an ethnonym is associated with the language family traditionally spoken or linked to that ethnic group.
-
E.
ethnicAspect
chosen
Indicates a relationship where one entity reflects, involves, or characterizes the ethnic background, identity, or attributes of another entity.
- 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_69ef1489f8b481908e24a1985982bd26 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f69383222c81909d8baa04129d5c81 |
completed | May 3, 2026, 12:14 a.m. |
| PD | Predicate disambiguation | batch_69f690eb1e948190aab41a89969519a5 |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 27, 2026, 8:48 a.m.