Triple
T9228539
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | California State Route 140 |
E221751
|
entity |
| Predicate | touristRouteFor |
P17534
|
FINISHED |
| Object | Yosemite National Park visitors |
—
|
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: Yosemite National Park visitors | Statement: [California State Route 140, touristRouteFor, Yosemite National Park visitors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: touristRouteFor Context triple: [California State Route 140, touristRouteFor, Yosemite National Park visitors]
-
A.
travelRouteOf
Indicates the path or itinerary that an entity follows or uses when traveling from one location to another.
-
B.
hasTouristRoute
chosen
Indicates that a location or site is connected to or included in a designated tourist route or itinerary.
-
C.
popularRouteFrom
Indicates a frequently chosen or well-traveled route that starts from a given origin location.
-
D.
pilgrimageRouteTo
Indicates a route or path that is traditionally used or designated for making a religious or spiritual pilgrimage to a particular destination.
-
E.
tourWith
Indicates that one entity accompanies another on a tour, sharing the same itinerary or guided experience.
- 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_69ca83ec8db08190a9110df8232885d2 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccdaa1c5b4819081dac6713053a8ae |
completed | April 1, 2026, 8:43 a.m. |
| PD | Predicate disambiguation | batch_69cc7a3daeb481908b0abde3fbc1f1f0 |
completed | April 1, 2026, 1:51 a.m. |
Created at: March 30, 2026, 7:29 p.m.