Triple
T31124578
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bayandur |
E793319
|
entity |
| Predicate | socioPoliticalType |
P103958
|
FINISHED |
| Object | nomadic-tribal group |
—
|
LITERAL 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: nomadic-tribal group | Statement: [Bayandur, socioPoliticalType, nomadic-tribal group]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: socioPoliticalType Context triple: [Bayandur, socioPoliticalType, nomadic-tribal group]
-
A.
socioPoliticalDomainOf
Indicates the socio-political sphere, context, or domain within which an entity, action, or relationship is situated or exerts influence.
-
B.
typeOfPolity
chosen
Indicates that one entity is a political unit and the other specifies the kind or classification of that polity (e.g., empire, kingdom, republic).
-
C.
associatedPoliticalSystem
Indicates that there exists a political system with which the subject is formally or conceptually connected.
-
D.
politicalCategory
Indicates the political classification or ideological grouping that an entity belongs to or is associated with.
-
E.
politicalForm
Indicates the type or structure of governance or political organization that characterizes an 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_69f224d1701c819094f429798290e361 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69c234d648190a243fb2b107136a9 |
completed | May 3, 2026, 12:51 a.m. |
| PD | Predicate disambiguation | batch_69f69665cd9c819088c388fc82fec42e |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 9:05 p.m.