Triple
T33144894
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cameron, Arizona |
E848262
|
entity |
| Predicate | nearestGrandCanyonEntrance |
P74849
|
FINISHED |
| Object | East Entrance at Desert View |
—
|
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: East Entrance at Desert View | Statement: [Cameron, Arizona, nearestGrandCanyonEntrance, East Entrance at Desert View]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearestGrandCanyonEntrance Context triple: [Cameron, Arizona, nearestGrandCanyonEntrance, East Entrance at Desert View]
-
A.
nearestNationalParkEntrance
chosen
Indicates the relationship where a given location is associated with the closest entrance point of a national park.
-
B.
nearestNationalParkHeadquarters
Indicates that one location is the closest national park headquarters to another specified place.
-
C.
nearbyCanyon
Indicates that one entity is located close to a canyon in spatial proximity.
-
D.
nearestEntrance
Indicates that one entrance is the closest access point to a given location or entity compared to all other possible entrances.
-
E.
nearestNationalForestAccess
Indicates the closest access point or entrance to a national forest relative to a given location.
- 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_69f3495a458c8190a1d34b237ba0be3f |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f7431c0eec81909ead443e07d75e18 |
completed | May 3, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69f74143cf708190a12d487884298437 |
completed | May 3, 2026, 12:36 p.m. |
Created at: May 1, 2026, 1:28 a.m.