Triple
T35813641
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vienna Stadtbahn |
E1035296
|
entity |
| Predicate | infrastructureReusedBy |
P91997
|
FINISHED |
| Object | U4 line of Vienna U-Bahn |
—
|
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: U4 line of Vienna U-Bahn | Statement: [Vienna Stadtbahn, infrastructureReusedBy, U4 line of Vienna U-Bahn]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: infrastructureReusedBy Context triple: [Vienna Stadtbahn, infrastructureReusedBy, U4 line of Vienna U-Bahn]
-
A.
infrastructureReuse
Indicates that existing infrastructure is being used again for a new or continued purpose instead of building or deploying entirely new infrastructure.
-
B.
reusedIn
chosen
Indicates that something previously used in one context or instance is used again in another context or instance.
-
C.
usesInfrastructure
Indicates that one entity makes use of, depends on, or operates through the infrastructure provided or managed by another entity.
-
D.
infrastructureAssociatedWith
Indicates a relationship where a piece of infrastructure is functionally or contextually connected to, supports, or is used by another entity.
-
E.
preservesInfrastructureOf
Indicates that one entity maintains, protects, or sustains the functionality and integrity of another entity’s infrastructure.
- 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_69f76e1762408190b885a8456862e372 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7aa699d68819081ed363931894ab3 |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8d219f8819081dc4ce3c83ca0cb |
completed | May 3, 2026, 7:58 p.m. |
Created at: May 3, 2026, 4:06 p.m.