Triple
T4149338
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gitxsan |
E89864
|
entity |
| Predicate | hasLandClaim |
P647
|
FINISHED |
| Object | Gitxsan title and rights claim |
—
|
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: Gitxsan title and rights claim | Statement: [Gitxsan, hasLandClaim, Gitxsan title and rights claim]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLandClaim Context triple: [Gitxsan, hasLandClaim, Gitxsan title and rights claim]
-
A.
hasLandStatus
Indicates that an entity possesses a particular legal or administrative status regarding land (such as ownership, tenure, protection, or use designation).
-
B.
hasLandComponent
Indicates that something includes, consists of, or is associated with a land-based part or portion as one of its components.
-
C.
hasLandAllotmentDescribedIn
Indicates that an entity’s land allotment is specified or detailed in a particular document or description.
-
D.
claimsTerritory
chosen
Indicates that one entity asserts ownership, control, or sovereign rights over a specific geographic area or region.
-
E.
sovereigntyClaim
Indicates a claim by one entity that it possesses supreme authority or governing rights over a territory, population, or domain, regardless of recognition by others.
- 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_69aed95a59a881909b26e70b42c6811a |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af033ef6648190adde17f943d89c78 |
completed | March 9, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69af018c101081909070da5b11e5eb3d |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:43 p.m.