Triple
T24728155
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1987 Constitutional Accord |
E618210
|
entity |
| Predicate | initiallyAgreedBy |
P111624
|
FINISHED |
| Object | federal government of Canada |
—
|
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: federal government of Canada | Statement: [1987 Constitutional Accord, initiallyAgreedBy, federal government of Canada]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: initiallyAgreedBy Context triple: [1987 Constitutional Accord, initiallyAgreedBy, federal government of Canada]
-
A.
agreementSignedBy
Indicates that a particular agreement has been formally signed or executed by a specified party.
-
B.
confirmedAgreementBetween
chosen
Indicates that a previously proposed agreement between two or more parties has been formally verified, accepted, and is now recognized as valid.
-
C.
agreedAt
Indicates the time or point at which an agreement or consensus between parties was reached.
-
D.
formedByAgreementWith
Indicates that something comes into existence or is established as a direct result of a formal agreement between parties.
-
E.
agreementSigned
Indicates that a formal agreement or contract has been officially signed and accepted by the involved parties.
- 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.