Triple
T36068706
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hōan |
E1043305
|
entity |
| Predicate | hasReigningEmperor |
P10335
|
FINISHED |
| Object | Emperor Toba |
E320721
|
NE 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: Emperor Toba | Statement: [Hōan, hasReigningEmperor, Emperor Toba]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReigningEmperor Context triple: [Hōan, hasReigningEmperor, Emperor Toba]
-
A.
hasEmperor
chosen
Indicates that an entity is ruled or governed by an emperor.
-
B.
reigningEmperorAtStart
Indicates that the subject was the emperor in power at the beginning of a specified period or event.
-
C.
recentEnthronementEmperor
Indicates that an individual has very recently assumed the position of emperor through an enthronement event.
-
D.
hasNotableEmperor
Indicates that an entity is associated with at least one emperor who is historically recognized as particularly important or distinguished.
-
E.
reigningEmperorPersonalName
Indicates the personal name of the individual who is currently serving as the reigning emperor.
- F. None of above.
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_69f76e2fd3248190b900d9a492bf5a7a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a39cfb0358c8190a05555a4ee81314a |
completed | June 23, 2026, 12:13 a.m. |
| PD | Predicate disambiguation | batch_6a037a0895b48190acdd88dc10db7be7 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:08 p.m.