Triple
T31365239
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chickasaw people |
E799990
|
entity |
| Predicate | primaryReservationIn |
P207413
|
FINISHED |
| Object | Oklahoma |
E34528
|
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: Oklahoma | Statement: [Chickasaw people, primaryReservationIn, Oklahoma]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryReservationIn Context triple: [Chickasaw people, primaryReservationIn, Oklahoma]
-
A.
primaryReservationState
Indicates the main or current status assigned to a reservation within its lifecycle.
-
B.
primaryReservationLocation
Indicates the main or default location associated with a reservation where it is primarily held or fulfilled.
-
C.
isPrimaryReservationOf
Indicates that a given reservation is the main or designated primary booking associated with a particular entity (such as a person, account, or resource).
-
D.
mainReserve
Indicates that one entity serves as the primary or main reserve resource, backup, or store for another entity.
-
E.
hasPrimaryReservation
Indicates that an entity holds the main or first-priority reservation associated with another entity or resource.
- F. None of above. chosen
Provenance (5 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_69f224e6b7448190ac6bf97ad7364160 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2ad22e9c648190bed1d07098e9d2a1 |
completed | June 11, 2026, 3:20 p.m. |
| PD | Predicate disambiguation | batch_6a0379e5174c8190a0bdde7e381b7624 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7ee0388190a29faeb5cdb0950a |
completed | May 12, 2026, 7:16 p.m. |
Created at: April 29, 2026, 9:18 p.m.