Triple
T647668
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Havasupai people |
E11276
|
entity |
| Predicate | reservationArea |
P4090
|
FINISHED |
| Object | approximately 188,000 acres |
—
|
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: approximately 188,000 acres | Statement: [Havasupai people, reservationArea, approximately 188,000 acres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reservationArea Context triple: [Havasupai people, reservationArea, approximately 188,000 acres]
-
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.
reservedFor
Indicates that something is set aside or allocated specifically for the use, benefit, or purpose of a particular entity or group.
-
D.
representedArea
Indicates that one entity serves as a representation or depiction of a particular area or region.
-
E.
modernReservation
chosen
Indicates that an entity is a contemporary or currently active reservation associated with another entity (such as a group, person, or place).
- 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_69a493266a2881909daf4c40f719dee8 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49f1cb24481909d3b41a56b29dee9 |
completed | March 1, 2026, 8:18 p.m. |
| PD | Predicate disambiguation | batch_69a49d0c0dcc8190849211d45489a5a7 |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:36 p.m.