Triple
T6768324
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Meech Lake Accord |
E154978
|
entity |
| Predicate | opposedByGroup |
P73168
|
FINISHED |
| Object | some Indigenous leaders |
—
|
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: some Indigenous leaders | Statement: [Meech Lake Accord, opposedByGroup, some Indigenous leaders]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: opposedByGroup Context triple: [Meech Lake Accord, opposedByGroup, some Indigenous leaders]
-
A.
opposedBy
Indicates that one entity actively resists, disagrees with, or works against the actions, views, or position of another entity.
-
B.
opposedByLeader
Indicates that an action, proposal, or position is actively resisted or rejected by a leader.
-
C.
opposedConference
Indicates that one entity actively resists, counters, or works against another entity within the context of a conference or formal gathering.
-
D.
isOppositionCounterpartOf
Indicates a relationship where one entity serves as the opposing or counterpart force, side, or position to another within a conflict, competition, or contrast.
-
E.
opposedQualityTo
Indicates that one quality stands in direct opposition or contrast to another quality.
- 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_69c68812ef7c819099369f51febb725c |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d231b79c81908a4f7fa8f253706d |
completed | March 27, 2026, 6:53 p.m. |
| PD | Predicate disambiguation | batch_69c6d094105881909c5806eb4afa6306 |
completed | March 27, 2026, 6:46 p.m. |
| PDg | Predicate description generation | batch_69c6d1d5f1908190989efc8a2d18c965 |
completed | March 27, 2026, 6:52 p.m. |
Created at: March 27, 2026, 2:12 p.m.