Triple
T35672025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gwich’in Settlement Area |
E1030745
|
entity |
| Predicate | hasRightType |
P192878
|
FINISHED |
| Object | land rights |
—
|
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: land rights | Statement: [Gwich’in Settlement Area, hasRightType, land rights]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRightType Context triple: [Gwich’in Settlement Area, hasRightType, land rights]
-
A.
hasGoodType
Indicates that an entity possesses a type or classification considered appropriate, valid, or of high quality according to some defined criteria.
-
B.
haveType
Indicates that an entity belongs to or is classified under a specified type or category.
-
C.
hasRuntimeType
Indicates that an entity is of, or conforms to, a specific type when evaluated at runtime rather than at compile time.
-
D.
hasKeyType
Indicates that an entity possesses or is associated with a specific category or type of key.
-
E.
hasFaithfulType
Indicates that one entity has a corresponding type or classification that remains consistent, reliable, or invariant with respect to some underlying structure or mapping.
- F. None of above. chosen
Provenance (4 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_69f76e0acfc0819082c8495c2210ce73 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd2cf39b0c8190811b8a6fa9410560 |
completed | May 8, 2026, 12:23 a.m. |
| PD | Predicate disambiguation | batch_69fd2ad8dd988190a9899701ba00d917 |
completed | May 8, 2026, 12:14 a.m. |
| PDg | Predicate description generation | batch_69fd2cf29f808190856ab1d43a51d5c7 |
completed | May 8, 2026, 12:23 a.m. |
Created at: May 3, 2026, 4:05 p.m.