Triple
T27680404
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | West Entrance of Yellowstone National Park |
E697891
|
entity |
| Predicate | hasNearbyAccommodationIn |
P61766
|
FINISHED |
| Object | West Yellowstone, Montana |
—
|
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: West Yellowstone, Montana | Statement: [West Entrance of Yellowstone National Park, hasNearbyAccommodationIn, West Yellowstone, Montana]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyAccommodationIn Context triple: [West Entrance of Yellowstone National Park, hasNearbyAccommodationIn, West Yellowstone, Montana]
-
A.
hasNearbyLodge
Indicates that one entity is located close to or in the vicinity of a lodge associated with another entity.
-
B.
hasNearbyHotel
chosen
Indicates that one entity is located close to or within a short distance of a hotel.
-
C.
hasNearbyHotelCluster
Indicates that one or more hotels are located in close proximity to the referenced place or area, forming a spatial cluster.
-
D.
hasAccommodation
Indicates that an entity provides, owns, or is associated with a place for someone to stay or live.
-
E.
reservationNear
Indicates that a reservation is located geographically close to a specified reference entity 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_69ef590d458c81909583290c3cd0478b |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69fd2a215d6c8190a1a428ccaee603f1 |
completed | May 8, 2026, 12:11 a.m. |
| PD | Predicate disambiguation | batch_69fd28ef19688190bb8370f2812a43e7 |
completed | May 8, 2026, 12:06 a.m. |
Created at: April 27, 2026, 2:46 p.m.