Triple
T36068743
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tenji |
E1043306
|
entity |
| Predicate | eraSequenceInTobaReign |
P174198
|
FINISHED |
| Object | second era of Emperor Toba |
—
|
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: second era of Emperor Toba | Statement: [Tenji, eraSequenceInTobaReign, second era of Emperor Toba]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eraSequenceInTobaReign Context triple: [Tenji, eraSequenceInTobaReign, second era of Emperor Toba]
-
A.
eraSequence
Indicates that one era or time period directly follows or precedes another in a chronological sequence.
-
B.
eraSequenceInReign
chosen
Indicates the ordinal position of a specific era within the chronological sequence of eras that occur during a particular ruler’s reign.
-
C.
eraSequenceWithinDynasty
Indicates that one historical era occurs in a specific ordered position relative to another era within the same dynasty.
-
D.
eraSequenceInEmperorLingReign
Indicates that one era directly follows another within the chronological sequence of Emperor Ling’s reign.
-
E.
eraSequenceInEasternWu
Indicates that one era chronologically follows another within the historical sequence of Eastern Wu.
- 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_69f7b2c771108190adeec151daad5dab |
completed | May 3, 2026, 8:40 p.m. |
| PD | Predicate disambiguation | batch_69f7b1bad2e88190963ab4ee5d4f2038 |
completed | May 3, 2026, 8:36 p.m. |
Created at: May 3, 2026, 4:08 p.m.