Triple
T6774018
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charlottetown Accord |
E155109
|
entity |
| Predicate | referendumResult |
P73195
|
FINISHED |
| Object | defeated nationally |
—
|
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: defeated nationally | Statement: [Charlottetown Accord, referendumResult, defeated nationally]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: referendumResult Context triple: [Charlottetown Accord, referendumResult, defeated nationally]
-
A.
referendumRelated
Indicates a relationship where something is connected to, associated with, or arising from a referendum process or its outcomes.
-
B.
heldReferendum
Indicates that an entity organized and conducted a referendum, typically allowing eligible participants to vote directly on a specific issue or proposal.
-
C.
referendumResultImplemented
Indicates that the outcome of a referendum has been put into effect through concrete actions or legal/administrative measures.
-
D.
subjectOfReferendum
Indicates that something is the issue, proposal, or matter being decided upon in a referendum.
-
E.
referendumDate
Indicates the specific date on which a referendum is scheduled to or did take place.
- 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_69c6d24c1b088190b99e9264b9b03dd8 |
completed | March 27, 2026, 6:54 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:13 p.m.