Triple
T19423570
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Klahoose First Nation |
E485920
|
entity |
| Predicate | isSignatoryOf |
P45747
|
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: [Klahoose First Nation, isSignatoryOf, modern treaty negotiations in British Columbia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSignatoryOf Context triple: [Klahoose First Nation, isSignatoryOf, modern treaty negotiations in British Columbia]
-
A.
wasSignatoryOf
Indicates that an entity formally signed or endorsed a specific document, agreement, or treaty as a participating party.
-
B.
agreementSignedBy
Indicates that a particular agreement has been formally signed or executed by a specified party.
-
C.
isTiritiSignatory
Indicates that an entity is a formal signatory to Te Tiriti o Waitangi (the Treaty of Waitangi).
-
D.
signerOf
chosen
Indicates that an entity has signed or formally endorsed a document, agreement, or statement.
-
E.
foundingSignatory
Indicates that an entity was an original signer or member at the founding of another entity, agreement, or organization.
- 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_69d8e8d688f881909c85104a62e09d8a |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e632169d9c81909a88704c6beb8fe0 |
completed | April 20, 2026, 2:03 p.m. |
| PD | Predicate disambiguation | batch_69e4fd68b1f881908d273de1fee81a75 |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:37 p.m.