Triple
T3210185
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Salt River Pima-Maricopa Indian Community |
E67259
|
entity |
| Predicate | reservationType |
P45275
|
FINISHED |
| Object | Indian reservation |
—
|
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: Indian reservation | Statement: [Salt River Pima-Maricopa Indian Community, reservationType, Indian reservation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reservationType Context triple: [Salt River Pima-Maricopa Indian Community, reservationType, Indian reservation]
-
A.
reservationSystem
Indicates a system or process that manages the creation, modification, and tracking of reservations or bookings between parties.
-
B.
reservationPolicy
Indicates the rules or conditions governing how reservations are made, modified, or canceled between parties.
-
C.
hasReservationType
chosen
Indicates that an entity is associated with a specific category or type of reservation.
-
D.
reservationState
Indicates the current status or phase of a reservation within its lifecycle (e.g., pending, confirmed, canceled, completed).
-
E.
allowsReservation
Indicates that one entity permits another entity to make or hold a reservation for its use or access.
- 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_69ad858ac36c81909962589cd277d6e2 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69adaab701c48190b91404ab416f7ce3 |
completed | March 8, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69ad9e09b83881908801d79c3d9254f9 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:07 p.m.