Triple
T4127624
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nisga’a |
E92762
|
entity |
| Predicate | treatyLandOwnership |
P34249
|
FINISHED |
| Object | fee simple Nisga’a lands |
—
|
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: fee simple Nisga’a lands | Statement: [Nisga’a, treatyLandOwnership, fee simple Nisga’a lands]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: treatyLandOwnership Context triple: [Nisga’a, treatyLandOwnership, fee simple Nisga’a lands]
-
A.
landTenure
chosen
Indicates the type, conditions, or rights under which land is held, used, or owned by an entity.
-
B.
landPolicy
Indicates a relationship where an authority defines or applies rules governing the ownership, use, management, or distribution of land.
-
C.
treatyScope
Indicates the range, subject matter, or extent of issues and obligations that a treaty covers or applies to.
-
D.
treatyOrLegalIssue
Indicates a formal agreement, dispute, or matter governed by treaties or legal frameworks between parties.
-
E.
treaty
Indicates a formal, negotiated agreement or pact established between entities, typically states or organizations, that defines mutual obligations, rights, or terms of cooperation.
- 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_69aed9685f70819086932777aec8d959 |
completed | March 9, 2026, 2:30 p.m. |
| NER | Named-entity recognition | batch_69af03a0f3408190adba7a8513bd3d12 |
completed | March 9, 2026, 5:30 p.m. |
| PD | Predicate disambiguation | batch_69af01883b6c8190a482ead589a131a5 |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:42 p.m.