Triple
T5291406
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Norwegian throne |
E119749
|
entity |
| Predicate | successionLawEffectiveFrom |
P18557
|
FINISHED |
| Object | 1990 |
—
|
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: 1990 | Statement: [Norwegian throne, successionLawEffectiveFrom, 1990]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successionLawEffectiveFrom Context triple: [Norwegian throne, successionLawEffectiveFrom, 1990]
-
A.
successionLawStatus
Indicates the legal status or condition governing how succession or inheritance is determined or applied.
-
B.
successionLawChangeYear
chosen
Indicates the year in which a change to the rules or laws governing succession took effect.
-
C.
dateOfSuccession
Indicates the specific date on which one entity formally succeeded or took over a role, position, or title from another.
-
D.
successorAdoptionYear
Indicates the year in which a successor entity formally adopted or took over from its predecessor.
-
E.
successionDefinedBy
Indicates that the rules, order, or conditions of succession for one entity are determined or specified by another entity.
- 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_69bd446de5648190b313a90bd96730d2 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd8682d18c8190bbb35cc75c8a7c12 |
completed | March 20, 2026, 5:40 p.m. |
| PD | Predicate disambiguation | batch_69bd844dfdac819086efedd1cbebff84 |
completed | March 20, 2026, 5:30 p.m. |
Created at: March 20, 2026, 1:52 p.m.