Triple
T38151021
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ryakuō |
E952750
|
entity |
| Predicate | predecessorEraNorthernCourt |
P197346
|
FINISHED |
| Object | Kōei |
—
|
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ōei | Statement: [Ryakuō, predecessorEraNorthernCourt, Kōei]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: predecessorEraNorthernCourt Context triple: [Ryakuō, predecessorEraNorthernCourt, Kōei]
-
A.
predecessorEraRuler
Indicates that one ruler directly preceded another as the ruler of a given era or period.
-
B.
predecessorRulerEraSystem
Indicates that one ruler’s era or reign immediately preceded another’s within a defined ruling system or succession framework.
-
C.
predecessorAsEasternRuler
Indicates that one entity previously held the position of eastern ruler before another entity assumed that same role.
-
D.
successorInNorthernLands
Indicates that one entity becomes the next holder of a role, title, or position specifically within the context of the Northern Lands.
-
E.
precedesEra
Indicates that one time period or era occurs entirely before another in chronological order.
- 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_69fe87b609888190913b0c3f787ecdba |
completed | May 9, 2026, 1:02 a.m. |
| PD | Predicate disambiguation | batch_69fe8731af48819092084f6f74bf052d |
completed | May 9, 2026, 1 a.m. |
| PDg | Predicate description generation | batch_69fe87b52bd4819087d6d338fe47c97c |
completed | May 9, 2026, 1:02 a.m. |
Created at: May 3, 2026, 4:21 p.m.