Triple
T38151020
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ryakuō |
E952750
|
entity |
| Predicate | successorEraNorthernCourt |
P202967
|
FINISHED |
| Object | Kōtoku |
—
|
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: Kōtoku | Statement: [Ryakuō, successorEraNorthernCourt, Kōtoku]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorEraNorthernCourt Context triple: [Ryakuō, successorEraNorthernCourt, Kōtoku]
-
A.
predecessorEraNorthernCourt
Indicates that one era of the Northern Court immediately preceded another in chronological order.
-
B.
successorInNorthernLands
Indicates that one entity becomes the next holder of a role, title, or position specifically within the context of the Northern Lands.
-
C.
successorEmperorEra
Indicates that one emperor’s era directly follows and succeeds another emperor’s era in chronological order.
-
D.
successorEraRuler
Indicates that one ruler directly succeeds another as the ruler of a given era or period.
-
E.
establishedUnderDynasty
Indicates that something (such as an institution, structure, or entity) was founded or created during the rule of a specific dynasty.
- 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_69f76f0a67f4819080c492f61d688fcc |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a00d6aff0a08190a330dd0c7c1352f9 |
completed | May 10, 2026, 7:04 p.m. |
| PD | Predicate disambiguation | batch_6a00d60f2a508190aeaf5a9d8af9c39e |
completed | May 10, 2026, 7:01 p.m. |
| PDg | Predicate description generation | batch_6a00d6af4c588190a52f727a9dabd3dc |
completed | May 10, 2026, 7:04 p.m. |
Created at: May 3, 2026, 4:21 p.m.