Triple

T18005346
Position Surface form Disambiguated ID Type / Status
Subject Urach Waterfall E430730 entity
Predicate hasWalkingTimeFrom P53938 FINISHED
Object about 30–60 minutes from Bad Urach 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: about 30–60 minutes from Bad Urach | Statement: [Urach Waterfall, hasWalkingTimeFrom, about 30–60 minutes from Bad Urach]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasWalkingTimeFrom
Context triple: [Urach Waterfall, hasWalkingTimeFrom, about 30–60 minutes from Bad Urach]
  • A. hasApproximateWalkingTimeTo chosen
    Indicates that there is an estimated or approximate amount of time it takes to walk from one entity to another.
  • B. hasWalkingRouteType
    Indicates that an entity is associated with a specific type or category of walking route (e.g., trail, path, or walking itinerary).
  • C. hasNearbyWalkingRoutes
    Indicates that there are walkable paths or routes located close to the referenced entity.
  • D. hasWalkingRouteConnection
    Indicates that there is a walkable path or route directly connecting two locations.
  • E. reducedTravelTimeFrom
    Indicates that one entity has caused or experienced a decrease in the amount of time required to travel from a specified origin 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_69d8b904530081908bf341d842464856 completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e4b51ba1888190a339d726e92f376b completed April 19, 2026, 10:57 a.m.
PD Predicate disambiguation batch_69e3f90039e4819080527f860dca042e completed April 18, 2026, 9:34 p.m.
Created at: April 10, 2026, 10:24 a.m.