Triple
T24727857
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1980 Canadian federal election |
E618203
|
entity |
| Predicate | heldUnderMonarch |
P87991
|
FINISHED |
| Object | Elizabeth II |
—
|
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: Elizabeth II | Statement: [1980 Canadian federal election, heldUnderMonarch, Elizabeth II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heldUnderMonarch Context triple: [1980 Canadian federal election, heldUnderMonarch, Elizabeth II]
-
A.
heldUnderCivilRuler
chosen
Indicates that an event, position, or status occurred while a particular civil ruler was in power or authority.
-
B.
heldUnderDynasty
Indicates that an entity’s position, title, or authority was exercised during the rule of a specific dynasty.
-
C.
signedUnderMonarch
Indicates that a document or agreement was formally signed during the reign or authority of a specific monarch.
-
D.
monarchicalPowerExercisedBy
Indicates that monarchical authority or ruling power is exercised or carried out by a specified agent or entity.
-
E.
heldByHeirApparentOf
Indicates that something is possessed, controlled, or occupied by the heir apparent of a particular person, title, or position.
- 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_69e2fab772608190b74163751047ff50 |
completed | April 18, 2026, 3:29 a.m. |
| NER | Named-entity recognition | batch_69f410fe3b848190ae296a29f742ee30 |
completed | May 1, 2026, 2:33 a.m. |
| PD | Predicate disambiguation | batch_69f40ee8ada8819089a7016b50308ff0 |
completed | May 1, 2026, 2:24 a.m. |
Created at: April 18, 2026, 4:01 a.m.