Triple
T36068794
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ten’yō |
E1043308
|
entity |
| Predicate | followsReignEraOf |
P29666
|
FINISHED |
| Object | Emperor Toba |
—
|
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: Emperor Toba | Statement: [Ten’yō, followsReignEraOf, Emperor Toba]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followsReignEraOf Context triple: [Ten’yō, followsReignEraOf, Emperor Toba]
-
A.
followsEra
chosen
Indicates that one time period or era comes directly after another in chronological order.
-
B.
correspondsToReignOf
Indicates that something (such as a time period, event, or record) matches or is associated with the duration of a specific ruler’s reign.
-
C.
appliesAfterReignOf
Indicates that something becomes relevant, valid, or in effect only after the reign or rule of a specified entity has ended.
-
D.
originatedInReignOf
Indicates that something began, was initiated, or first came into existence during the rule or governing period of a particular ruler or authority.
-
E.
predecessorRulerEraSystem
Indicates that one ruler’s era or reign immediately preceded another’s within a defined ruling system or succession framework.
- 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_69f76e2fd3248190b900d9a492bf5a7a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ff255b84788190a94682f4efe1d0b8 |
completed | May 9, 2026, 12:15 p.m. |
| PD | Predicate disambiguation | batch_69ff24f3ab108190bb017a656cff3d82 |
completed | May 9, 2026, 12:13 p.m. |
Created at: May 3, 2026, 4:08 p.m.