Triple
T20021053
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Musqueam Indian Band |
E494856
|
entity |
| Predicate | isSignatoryTo |
P63848
|
FINISHED |
| Object | modern treaty negotiations in British Columbia |
—
|
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: modern treaty negotiations in British Columbia | Statement: [Musqueam Indian Band, isSignatoryTo, modern treaty negotiations in British Columbia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSignatoryTo Context triple: [Musqueam Indian Band, isSignatoryTo, modern treaty negotiations in British Columbia]
-
A.
isTiritiSignatory
Indicates that an entity is a formal signatory to Te Tiriti o Waitangi (the Treaty of Waitangi).
-
B.
wasSignatoryOf
chosen
Indicates that an entity formally signed or endorsed a specific document, agreement, or treaty as a participating party.
-
C.
hasSignatories
Indicates that one or more parties have formally signed or endorsed an agreement, document, or instrument.
-
D.
isSignedAlong
Indicates that an entity has signed or endorsed something in conjunction with another specified entity.
-
E.
agreementSignedBy
Indicates that a particular agreement has been formally signed or executed by a specified party.
- 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_69da626bfd288190aa5d65098b6433ae |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e6623fe1988190a1c09d392d866dc8 |
completed | April 20, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69e54cdddbd48190becc8b2aa5ab4ef9 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:34 p.m.