Triple
T29545948
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Louisiana Choctaw |
E749629
|
entity |
| Predicate | associatedWithReservationOrCommunity |
P109405
|
FINISHED |
| Object | Louisiana Choctaw communities |
E749629
|
NE 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: Louisiana Choctaw communities | Statement: [Louisiana Choctaw, associatedWithReservationOrCommunity, Louisiana Choctaw communities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithReservationOrCommunity Context triple: [Louisiana Choctaw, associatedWithReservationOrCommunity, Louisiana Choctaw communities]
-
A.
associatedWithReservation
chosen
Indicates that one entity has a connection or linkage to a specific reservation.
-
B.
notableReservationCommunity
Indicates that a community is notably associated with or recognized for a particular reservation.
-
C.
isPartOfReservation
Indicates that one entity belongs to, or is included within, a specific reservation.
-
D.
hasResortCommunity
Indicates that one entity includes, contains, or is associated with a resort-style residential or vacation community.
-
E.
recognizedAsReservationBy
Indicates that something is acknowledged or accepted as a reservation by a particular party or system.
- F. None of above.
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_69f0bd48691081908cecad39bac591e0 |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a260c4184648190b21de658660fe246 |
completed | June 8, 2026, 12:26 a.m. |
| PD | Predicate disambiguation | batch_6a0379e0f3d88190a4ee7b0673f1ef90 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 28, 2026, 5:07 p.m.