Triple

T29359927
Position Surface form Disambiguated ID Type / Status
Subject Perusastraße E744558 entity
Predicate hasTransportConnectionNearby P3791 FINISHED
Object Munich U-Bahn station Odeonsplatz NE NERFINISHED

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: Munich U-Bahn station Odeonsplatz | Statement: [Perusastraße, hasTransportConnectionNearby, Munich U-Bahn station Odeonsplatz]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasTransportConnectionNearby
Context triple: [Perusastraße, hasTransportConnectionNearby, Munich U-Bahn station Odeonsplatz]
  • A. hasTransportationProximityTo
    Indicates that one entity is located near or conveniently accessible to another entity in terms of transportation options or routes.
  • B. hasPublicTransportConnection chosen
    Indicates that there is an available public transportation link or service connecting the related entities.
  • C. hasNearbyAccess
    Indicates that one entity has convenient, close-proximity access to another resource, service, or location.
  • D. hasNearbyTransportationCorridor
    Indicates that an entity is located close to a significant transportation route or corridor, such as a road, railway, or transit line.
  • E. hasNearbyInterchange
    Indicates that one location has a transportation interchange (such as a junction or transfer point) situated close to it.
  • 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_69f0a79aee588190b490f19d93c6e52d completed April 28, 2026, 12:27 p.m.
NER Named-entity recognition batch_69fdd5fba5048190b7d430ae2054a1fd completed May 8, 2026, 12:24 p.m.
PD Predicate disambiguation batch_69fdd35f76f88190a1854ea27132f9c7 completed May 8, 2026, 12:13 p.m.
Created at: April 28, 2026, 2:16 p.m.