Triple
T4719865
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cocopah Indian Reservation |
E104736
|
entity |
| Predicate | tribeStatus |
P58167
|
FINISHED |
| Object | Federally recognized tribe |
—
|
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: Federally recognized tribe | Statement: [Cocopah Indian Reservation, tribeStatus, Federally recognized tribe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tribeStatus Context triple: [Cocopah Indian Reservation, tribeStatus, Federally recognized tribe]
-
A.
tribalStatus
chosen
Indicates that an entity holds a particular affiliation, recognition, or classification with respect to a tribe or tribal community.
-
B.
stateRecognizedTribe
Indicates that a tribe is officially acknowledged and recognized by a state government as a tribal entity.
-
C.
tribalOrganization
Indicates that an entity is organized as, or formally recognized as, a tribal governing or social structure.
-
D.
hasTribalMembersFrom
Indicates that an entity includes or is composed of members originating from a specified tribe or tribal group.
-
E.
recognizedTribe
Indicates that a group is officially acknowledged as a tribe by a governing or authoritative body.
- 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_69bd43ec4a348190bc41afae43375e71 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd680beb508190b3d74e20e1c64405 |
completed | March 20, 2026, 3:30 p.m. |
| PD | Predicate disambiguation | batch_69bd621ddcd88190903288566f5e5dab |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:18 p.m.