Triple
T17460460
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Daigo-tennō |
E425137
|
entity |
| Predicate | ordinalInJapaneseImperialLine |
P51882
|
FINISHED |
| Object | 60 |
—
|
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: 60 | Statement: [Daigo-tennō, ordinalInJapaneseImperialLine, 60]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ordinalInJapaneseImperialLine Context triple: [Daigo-tennō, ordinalInJapaneseImperialLine, 60]
-
A.
rankInJapaneseOrders
Indicates the position or level an entity holds within the hierarchy of Japanese orders, decorations, or honors.
-
B.
eraNumberInJapan
Indicates the specific numbered position of a historical era within the sequence of Japanese eras.
-
C.
hasEmperorPosthumousName
Indicates that an individual has been granted or is known by a specific posthumous name used for emperors.
-
D.
associatedDynasticOrder
Indicates a relationship where an entity is linked to, or formally connected with, a particular dynastic order.
-
E.
ordinalNumberAsEmperor
chosen
Indicates the numerical order in which a person held the title or role of emperor.
- 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_69d889db0ba481908402409af3b37917 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e451a3031c8190ab1dd0d41b002dd2 |
completed | April 19, 2026, 3:53 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f0e3fc819094e466b74622c956 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:47 a.m.