Triple
T37705743
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | S2 line (Vienna) |
E939192
|
entity |
| Predicate | connectsCentralHubs |
P111188
|
FINISHED |
| Object | Praterstern |
—
|
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: Praterstern | Statement: [S2 line (Vienna), connectsCentralHubs, Praterstern]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectsCentralHubs Context triple: [S2 line (Vienna), connectsCentralHubs, Praterstern]
-
A.
connectsCentralAreaTo
Indicates a relationship where one element serves as a link or pathway between a central area and another location or component.
-
B.
connectsMajorHub
chosen
Indicates that one entity serves as a link or route between major hubs or primary nodes in a network.
-
C.
isCentralHubOf
Indicates that one entity functions as the primary connecting or coordinating hub for activities, resources, or interactions among multiple other entities.
-
D.
connectsTypeOfHub
Indicates that one entity is linked to another entity that functions as a specific type of hub within a network or system.
-
E.
connectsCentralDistrictsWith
Indicates a relationship where something serves as a link or route joining central districts to one another.
- 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_69f76edb49dc8190b951dce9ce6ef789 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fffc783b648190bcd7df017514d206 |
completed | May 10, 2026, 3:33 a.m. |
| PD | Predicate disambiguation | batch_69fffc03fa24819099e12413dc6e0afd |
completed | May 10, 2026, 3:31 a.m. |
Created at: May 3, 2026, 4:18 p.m.