Triple
T19589986
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Modoc Nation |
E470204
|
entity |
| Predicate | hasTribalCode |
P51730
|
FINISHED |
| Object | Modoc Nation tribal laws |
—
|
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: Modoc Nation tribal laws | Statement: [Modoc Nation, hasTribalCode, Modoc Nation tribal laws]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTribalCode Context triple: [Modoc Nation, hasTribalCode, Modoc Nation tribal laws]
-
A.
tribalCode
chosen
Indicates that an entity is governed by, associated with, or identified according to a specific tribal legal or regulatory code.
-
B.
hasTribalAssociation
Indicates that an entity is affiliated with, belongs to, or is formally associated with a particular tribe or tribal group.
-
C.
hasTribalRegister
Indicates that an entity is officially recorded or listed in a recognized tribal registry or roll.
-
D.
hasTribalEntity
Indicates that one entity is associated with, belongs to, or is part of a specific tribal group or tribal organizational body.
-
E.
hasTribalPresence
Indicates that a tribal group is present, active, or represented in relation to the referenced entity or location.
- 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_69d8e510024481908415c0d616fa6186 |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e640552db48190b34555e4b72a75c4 |
completed | April 20, 2026, 3:03 p.m. |
| PD | Predicate disambiguation | batch_69e514dbdb988190b55931a8138c73e7 |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:43 p.m.