Triple

T31421359
Position Surface form Disambiguated ID Type / Status
Subject A7 motorway (Germany) E801536 entity
Predicate terminusNearCity P137070 FINISHED
Object Füssen 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: Füssen | Statement: [A7 motorway (Germany), terminusNearCity, Füssen]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: terminusNearCity
Context triple: [A7 motorway (Germany), terminusNearCity, Füssen]
  • A. terminusNearbySettlement chosen
    Indicates that a transportation terminus (such as a station or terminal) is located close to a particular settlement.
  • B. nearbyTerminus
    Indicates that one terminus (end point or final stop) is located close to another terminus in space.
  • C. terminusCity
    Indicates that a transportation route or service ends or has its final stop in a particular city.
  • D. terminusWestNear
    Indicates that the western terminus of one entity is located near the western terminus of another entity.
  • E. terminusSouthNear
    Indicates that the southern end or terminus of one entity is located close 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_69f348c26f048190b4adadd71b4596c5 completed April 30, 2026, 12:19 p.m.
NER Named-entity recognition batch_69f72921cf2c8190909bb53f78bcc890 completed May 3, 2026, 10:53 a.m.
PD Predicate disambiguation batch_69f7283d8cec8190b524c144948bc4ec completed May 3, 2026, 10:49 a.m.
Created at: April 30, 2026, 8:48 p.m.