Triple
T7531017
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chillon Castle |
E178021
|
entity |
| Predicate | nearTransportRoute |
P61362
|
FINISHED |
| Object | road between Montreux and Villeneuve |
—
|
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: road between Montreux and Villeneuve | Statement: [Chillon Castle, nearTransportRoute, road between Montreux and Villeneuve]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearTransportRoute Context triple: [Chillon Castle, nearTransportRoute, road between Montreux and Villeneuve]
-
A.
transportationNearby
Indicates that there is a transportation facility or service located close to the referenced entity.
-
B.
nearestRoadHead
Indicates that one location is the closest accessible road endpoint (or road access point) to another location.
-
C.
nearbyTransit
Indicates that one location has public transportation options situated within a short distance or easy access from it.
-
D.
hasNearbyWalkingRoutes
Indicates that there are walkable paths or routes located close to the referenced entity.
-
E.
nearbyTo
chosen
Indicates that one entity is located close in distance or position to another entity.
- 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_69c69f2acdbc8190b5a8320168c1d0ba |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f8217b1c8190b3db453cee0fc4fd |
completed | March 27, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69c6f4d6bb808190bdd04499fd3bceb6 |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:47 p.m.