Triple

T5987973
Position Surface form Disambiguated ID Type / Status
Subject Rügen Bridge E133274 entity
Predicate hasEmergencyLane P67768 FINISHED
Object yes 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: yes | Statement: [Rügen Bridge, hasEmergencyLane, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasEmergencyLane
Context triple: [Rügen Bridge, hasEmergencyLane, yes]
  • A. hasDedicatedLanes
    Indicates that specific lanes within a route or roadway are reserved exclusively for a particular type of traffic or use.
  • B. hasLanes
    Indicates that an entity, such as a road or pathway, is divided into one or more distinct lanes for traffic or movement.
  • C. hasWheelchairLanes
    Indicates that a location, route, or facility includes designated lanes or pathways specifically designed for wheelchair use.
  • D. hasExpressLanes
    Indicates that a roadway or transportation facility includes designated express lanes for faster or prioritized travel.
  • E. hasLightningLane
    Indicates that an attraction, experience, or location offers access via a Lightning Lane queue or reservation system.
  • F. None of above. chosen

Provenance (4 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_69c0087010d081908bb8142342d63330 completed March 22, 2026, 3:19 p.m.
NER Named-entity recognition batch_69c04dc51d948190bacf4c40a73e91b2 completed March 22, 2026, 8:15 p.m.
PD Predicate disambiguation batch_69c049de98648190962b14fd341c93da completed March 22, 2026, 7:58 p.m.
PDg Predicate description generation batch_69c04a663a4481908983048c69cba6b6 completed March 22, 2026, 8 p.m.
Created at: March 22, 2026, 4:04 p.m.