Triple

T14405374
Position Surface form Disambiguated ID Type / Status
Subject U-Bahnhof Seestraße E357181 entity
Predicate isInterchangeNode P84508 FINISHED
Object ja 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: ja | Statement: [U-Bahnhof Seestraße, isInterchangeNode, ja]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isInterchangeNode
Context triple: [U-Bahnhof Seestraße, isInterchangeNode, ja]
  • A. isInterchangeBetween
    Indicates a relationship where something serves as a point or medium through which two or more entities can exchange or transfer items, information, or traffic between each other.
  • B. isInterchange
    Indicates that two entities can be substituted or exchanged for one another without affecting the relevant system, function, or outcome.
  • C. isInterchangeWith
    Indicates that two entities can be substituted or exchanged for one another without loss of function, value, or compatibility.
  • D. hasInterchangeRole
    Indicates that one entity serves in a role that allows it to be exchanged or substituted with another entity within a given context or system.
  • E. isPartOfInterchangeComplex chosen
    Indicates that one transportation facility or component belongs to and functions within a larger interchange complex.
  • 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_69d82793421c8190861eb0e673b085de completed April 9, 2026, 10:26 p.m.
NER Named-entity recognition batch_69de908804048190a4fe58afc2e0a5b6 completed April 14, 2026, 7:07 p.m.
PD Predicate disambiguation batch_69de2aa1b57881909a033eac8545c417 completed April 14, 2026, 11:53 a.m.
Created at: April 10, 2026, 1:17 a.m.