Triple
T31908563
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tonyukuk |
E814619
|
entity |
| Predicate | advisedRuler |
P172722
|
FINISHED |
| Object | Qapaghan Qaghan |
—
|
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: Qapaghan Qaghan | Statement: [Tonyukuk, advisedRuler, Qapaghan Qaghan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: advisedRuler Context triple: [Tonyukuk, advisedRuler, Qapaghan Qaghan]
-
A.
rulerOf
Indicates that one entity holds governing authority or sovereignty over another entity, such as a person ruling a country or territory.
-
B.
monarchWhoGrants
Indicates a relationship where a monarch bestows, confers, or grants something (such as rights, titles, lands, or privileges) to another party.
-
C.
possibleRuler
Indicates that one entity is a potential or candidate ruler of another entity, without asserting that the rulership is actual or confirmed.
-
D.
fatherIsRulerOf
Indicates that the person who is the father holds the position of ruler or sovereign over the specified entity or domain.
-
E.
patronRuler
Indicates a relationship where one entity serves as a protective or sponsoring ruler or sovereign authority over another.
- 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_69f348f109d88190b5005372c53d2fcd |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b1b6a1f08190b1d5306ae35977cb |
completed | May 3, 2026, 2:23 a.m. |
| PD | Predicate disambiguation | batch_69f6aca59d4881908d14ed47962703bd |
completed | May 3, 2026, 2:02 a.m. |
| PDg | Predicate description generation | batch_69f6af7d92008190aead47eaae8cc091 |
completed | May 3, 2026, 2:14 a.m. |
Created at: May 1, 2026, 12:01 a.m.