Triple
T31124576
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bayandur |
E793319
|
entity |
| Predicate | statusWithinOghuz |
P196183
|
FINISHED |
| Object | prominent tribe |
—
|
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: prominent tribe | Statement: [Bayandur, statusWithinOghuz, prominent tribe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusWithinOghuz Context triple: [Bayandur, statusWithinOghuz, prominent tribe]
-
A.
notUnderFullOttomanControl
Indicates that the entity or region was not completely governed, administered, or dominated by the Ottoman Empire.
-
B.
outcomeForOttomans
Indicates the result or consequence experienced by the Ottoman side in a given event, action, or situation.
-
C.
OttomanStrength
Indicates the level or degree of military, political, or economic power possessed or exerted by the Ottoman Empire in a given context.
-
D.
statusInTurkey
Indicates the legal, social, or official condition or standing that an entity holds within the context of Turkey.
-
E.
usedTurkishGuard
Indicates that an entity employed or utilized a Turkish guard in some capacity.
- F. None of above. chosen
Provenance (4 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_69fe12a899d4819080d48423f32eace9 |
completed | May 8, 2026, 4:43 p.m. |
| PD | Predicate disambiguation | batch_69fe0d7f6aa08190a1d2dfc025d4e0dc |
completed | May 8, 2026, 4:21 p.m. |
| PDg | Predicate description generation | batch_69fe12a769c08190bc445d302d2e8f98 |
completed | May 8, 2026, 4:43 p.m. |
Created at: April 29, 2026, 9:05 p.m.