Triple
T27058957
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ribbon Falls spur junction |
E684981
|
entity |
| Predicate | accessesPopularDestination |
P146014
|
FINISHED |
| Object | Ribbon Falls |
—
|
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: Ribbon Falls | Statement: [Ribbon Falls spur junction, accessesPopularDestination, Ribbon Falls]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: accessesPopularDestination Context triple: [Ribbon Falls spur junction, accessesPopularDestination, Ribbon Falls]
-
A.
journeyDestination
Indicates that one entity serves as the endpoint or intended destination of another entity’s journey or travel.
-
B.
tourismTrend
Indicates how patterns or levels of tourism activity change over time or across locations.
-
C.
notableDestination
Indicates that a location is recognized as a significant or prominent place that people commonly travel to or aim to visit.
-
D.
popularRouteTo
chosen
Indicates that one location is widely used or frequently chosen as a route or way to reach another location.
-
E.
isPopularTouristDestinationIn
Indicates that a place is widely visited and favored by tourists within a specified geographic area or region.
- 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_69ef14829fac8190914bef9ecc3005d7 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f66c5c13808190887180099745673b |
completed | May 2, 2026, 9:27 p.m. |
| PD | Predicate disambiguation | batch_69f66abddc448190a488852f8abdeb2c |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 27, 2026, 8:20 a.m.