Triple

T23524020
Position Surface form Disambiguated ID Type / Status
Subject Cityrunner Vienna type E574583 entity
Predicate trackCompatibility P48645 FINISHED
Object Vienna tram infrastructure 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: Vienna tram infrastructure | Statement: [Cityrunner Vienna type, trackCompatibility, Vienna tram infrastructure]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: trackCompatibility
Context triple: [Cityrunner Vienna type, trackCompatibility, Vienna tram infrastructure]
  • A. mechanicalCompatibility
    Indicates that two entities can function together properly from a mechanical standpoint, without interference, damage, or performance issues.
  • B. driftCompatibilityWith
    Indicates a relationship where two entities are capable of operating together in a highly synchronized, harmonious, or mutually adaptive manner.
  • C. compatibilityModel
    Indicates that one entity is defined or evaluated according to a specific compatibility framework, standard, or model in relation to another entity.
  • D. isGenerallyCompatibleWith chosen
    Indicates that two entities can typically function or coexist together without significant conflict, issues, or need for special adaptation.
  • E. compatibilityCondition
    Indicates that a specific requirement or set of criteria must be satisfied for two or more entities to be considered compatible or able to function together.
  • 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_69e245bb3dcc8190ba9a2b35972b58d0 completed April 17, 2026, 2:37 p.m.
NER Named-entity recognition batch_69f1ac71ec8881909bfb706efdc2518f completed April 29, 2026, 7 a.m.
PD Predicate disambiguation batch_69f1189d75b48190a1c01928a993c9fb completed April 28, 2026, 8:29 p.m.
Created at: April 17, 2026, 6:09 p.m.