Triple
T24365554
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tenno |
E614182
|
entity |
| Predicate | traditionalFirstEmperor |
P155934
|
FINISHED |
| Object | Emperor Jimmu |
—
|
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 Jimmu | Statement: [Tenno, traditionalFirstEmperor, Emperor Jimmu]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalFirstEmperor Context triple: [Tenno, traditionalFirstEmperor, Emperor Jimmu]
-
A.
firstEmperorToRuleAllChina
Indicates that the subject was the earliest emperor to unify and govern all of China under a single centralized rule.
-
B.
firstEmperorPersonalName
Indicates the personal (given) name of the individual who was the first emperor in a specified imperial line or polity.
-
C.
hasEmperor
Indicates that an entity is ruled or governed by an emperor.
-
D.
traditionalDynasty
Indicates a relationship where a dynasty is recognized as traditional, typically long-established and rooted in customary or historical authority.
-
E.
nativeDynasty
Indicates that a dynasty is indigenous to, or originally from, the place or polity it rules or is associated with.
- F. None of above. chosen
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_69e2d7dfe7f08190b7a1f3a36483ab05 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f293874f7c8190b472e99640e97f62 |
completed | April 29, 2026, 11:25 p.m. |
| PD | Predicate disambiguation | batch_69f287bb1b2c81909c2e7fcc392ad143 |
completed | April 29, 2026, 10:35 p.m. |
| PDg | Predicate description generation | batch_69f28f4d978c81908310c01def2514cc |
completed | April 29, 2026, 11:07 p.m. |
Created at: April 18, 2026, 2:01 a.m.