Triple
T30803419
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chickasaw Nation reservation |
E784433
|
entity |
| Predicate | hasTribalEnrollmentAuthority |
P98456
|
FINISHED |
| Object | Chickasaw Nation |
—
|
NE NERFINISHED |
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: Chickasaw Nation | Statement: [Chickasaw Nation reservation, hasTribalEnrollmentAuthority, Chickasaw Nation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTribalEnrollmentAuthority Context triple: [Chickasaw Nation reservation, hasTribalEnrollmentAuthority, Chickasaw Nation]
-
A.
hasTribalEnrollment
Indicates that an entity is formally enrolled as a member of a specific tribe or tribal nation.
-
B.
hasTribalAuthority
chosen
Indicates that an entity holds recognized governing or decision-making power within a specific tribe or tribal community.
-
C.
tribalEnrollmentBasis
Indicates the basis or criteria on which an individual’s enrollment or membership in a tribe is determined.
-
D.
hasTribalRegister
Indicates that an entity is officially recorded or listed in a recognized tribal registry or roll.
-
E.
linkedToTribalEnrollment
Indicates that one entity has a direct connection or association with another entity’s tribal enrollment status or record.
- 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_69f224b3a7ec819096939414d103e31e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fe991bca608190b524e419642f4243 |
completed | May 9, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69fe979fc1c4819091fc48d63ea12063 |
completed | May 9, 2026, 2:10 a.m. |
Created at: April 29, 2026, 8:42 p.m.