Triple
T30053963
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Entrance of Zion National Park |
E763675
|
entity |
| Predicate | nearbyServiceArea |
P61270
|
FINISHED |
| Object | Springdale lodging |
—
|
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: Springdale lodging | Statement: [South Entrance of Zion National Park, nearbyServiceArea, Springdale lodging]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearbyServiceArea Context triple: [South Entrance of Zion National Park, nearbyServiceArea, Springdale lodging]
-
A.
nearbyTo
Indicates that one entity is located close in distance or position to another entity.
-
B.
nearbyLocation
chosen
Indicates that one location is situated close to another location in physical space.
-
C.
nearbyUse
Indicates that one entity uses or operates another entity that is located nearby or in close physical proximity.
-
D.
naceCercaDe
Indicates that one entity is born or originates in close physical proximity to another entity.
-
E.
areaOfService
Indicates the geographic or functional region within which a service is provided or applicable.
- 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_69f224716378819087a722e487832b70 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fd2839880c819099a7a89783f2270e |
completed | May 8, 2026, 12:03 a.m. |
| PD | Predicate disambiguation | batch_69fd23dc5da48190ae8ba08947d34956 |
completed | May 7, 2026, 11:44 p.m. |
Created at: April 29, 2026, 6:56 p.m.