Triple
T30257287
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Succession to the Throne Act, 2013 (Canada) |
E769384
|
entity |
| Predicate | monarchConcerned |
P163091
|
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: [Succession to the Throne Act, 2013 (Canada), monarchConcerned, Elizabeth II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: monarchConcerned Context triple: [Succession to the Throne Act, 2013 (Canada), monarchConcerned, Elizabeth II]
-
A.
monarchInvolved
Indicates that a monarch participates in, is associated with, or plays a role in a particular event, action, or situation.
-
B.
monarchDuringIssue
chosen
Indicates that a specified person was the reigning monarch at the time a particular item, event, or issue occurred or was produced.
-
C.
monarchIn
Indicates that a person serves as the ruling monarch of a specified country, state, or territory.
-
D.
monarch
Indicates that an entity serves as the sovereign ruler (such as a king, queen, or emperor) over a state or territory.
-
E.
monarchTargeted
Indicates that a monarch is the specific object or target of an action, influence, or event.
- 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_69f22484a5f48190b678cd607700bc82 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6afebd7ec8190ab696f363d84abf0 |
completed | May 3, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69f6aca3dedc81908b519d53d2909868 |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 29, 2026, 7:41 p.m.