Triple

T11278746
Position Surface form Disambiguated ID Type / Status
Subject Washington Slagbaai National Park E267004 entity
Predicate hasDrivingRoutes P11026 FINISHED
Object long driving route 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: long driving route | Statement: [Washington Slagbaai National Park, hasDrivingRoutes, long driving route]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasDrivingRoutes
Context triple: [Washington Slagbaai National Park, hasDrivingRoutes, long driving route]
  • A. withinDrivingRoute
    Indicates that one location can be reached from another via a practical or allowable driving route, typically within a reasonable distance or time.
  • B. hasTransportRoute chosen
    Indicates that there exists a designated transportation connection or route linking one entity to another.
  • C. canProvideDirections
    Indicates that one entity is able to give another entity guidance or instructions on how to reach a particular location or navigate a route.
  • D. drivesOn
    Indicates that an entity uses or travels along a particular route, surface, or roadway as its path of movement.
  • E. hadTransportRoutes
    Indicates that there were established transportation routes or connections between the related entities.
  • 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_69d6aac8c2f48190ad0596f1f89f0470 completed April 8, 2026, 7:21 p.m.
NER Named-entity recognition batch_69d7e967ebb4819080b09ed3cec44e77 completed April 9, 2026, 6:01 p.m.
PD Predicate disambiguation batch_69d787a240588190aa097298f951c915 completed April 9, 2026, 11:04 a.m.
Created at: April 8, 2026, 9:31 p.m.