Triple
T23166367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mongol imperial family |
E578720
|
entity |
| Predicate | dynastyStart |
P125955
|
FINISHED |
| Object | 1206 |
—
|
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: 1206 | Statement: [Mongol imperial family, dynastyStart, 1206]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dynastyStart Context triple: [Mongol imperial family, dynastyStart, 1206]
-
A.
marksBeginningOfDynasty
Indicates that an event, person, or moment signifies the start or formal establishment of a particular dynasty.
-
B.
dynastyFoundedIn
chosen
Indicates that a particular dynasty was established or came into existence in a specified time or place.
-
C.
dynastyFoundedBecame
Indicates that an entity founded a dynasty and subsequently became its ruler or central figure.
-
D.
dynastyFoundedRuledPeriod
Indicates that a particular dynasty was founded and held ruling authority during a specified historical time period.
-
E.
dynastyConfirmed
Indicates that a particular ruling dynasty has been officially verified or recognized as legitimate in a given context.
- 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_69e245fc75348190a0288401044c8af8 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18f2c923c81908b58811fffdcf932 |
completed | April 29, 2026, 4:55 a.m. |
| PD | Predicate disambiguation | batch_69ef89ff76808190808ee4ad9dea776b |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 4:03 p.m.