Triple
T24728161
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1987 Constitutional Accord |
E618210
|
entity |
| Predicate | opposedByRole |
P21000
|
FINISHED |
| Object | Manitoba MLA |
—
|
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: Manitoba MLA | Statement: [1987 Constitutional Accord, opposedByRole, Manitoba MLA]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: opposedByRole Context triple: [1987 Constitutional Accord, opposedByRole, Manitoba MLA]
-
A.
opposedBy
Indicates that one entity actively resists, disagrees with, or works against the actions, views, or position of another entity.
-
B.
opposedByGroup
Indicates that an action, proposal, or entity is met with opposition or resistance from a particular group.
-
C.
opposedByLeader
Indicates that an action, proposal, or position is actively resisted or rejected by a leader.
-
D.
roleWhenInOpposition
chosen
Indicates the specific role or function an entity assumes when it is in a state of opposition to another entity or group.
-
E.
positionOpposed
Indicates that two entities hold positions or stances that are in direct conflict or opposition to each other.
- 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.