Triple
T36568473
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vuntut Gwitchin First Nation |
E902044
|
entity |
| Predicate | hasFinalAgreement |
P19828
|
FINISHED |
| Object | Vuntut Gwitchin First Nation Final Agreement |
—
|
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: Vuntut Gwitchin First Nation Final Agreement | Statement: [Vuntut Gwitchin First Nation, hasFinalAgreement, Vuntut Gwitchin First Nation Final Agreement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFinalAgreement Context triple: [Vuntut Gwitchin First Nation, hasFinalAgreement, Vuntut Gwitchin First Nation Final Agreement]
-
A.
agreedOn
Indicates that two or more parties have reached a mutual agreement or consensus regarding a specific matter, decision, or proposal.
-
B.
agreementOutcome
Indicates the result or consequence that follows from reaching or failing to reach an agreement between parties.
-
C.
hasFinalDecisionOn
Indicates that one entity holds the ultimate authority or responsibility to make and enforce a conclusive decision regarding another entity or matter.
-
D.
agreementSigned
chosen
Indicates that a formal agreement or contract has been officially signed and accepted by the involved parties.
-
E.
confirmedAgreementBetween
Indicates that a previously proposed agreement between two or more parties has been formally verified, accepted, and is now recognized as valid.
- 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_69f76e6416708190a9754b8c52d4e453 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a0027e4a59481909417b2531daaf480 |
completed | May 10, 2026, 6:38 a.m. |
| PD | Predicate disambiguation | batch_6a0026a42bc08190ad3322ce625a523a |
completed | May 10, 2026, 6:33 a.m. |
Created at: May 3, 2026, 4:11 p.m.