Triple
T3582072
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vienna station |
E75821
|
entity |
| Predicate | transitSystemType |
P18634
|
FINISHED |
| Object | rapid transit |
—
|
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: rapid transit | Statement: [Vienna station, transitSystemType, rapid transit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transitSystemType Context triple: [Vienna station, transitSystemType, rapid transit]
-
A.
partOfTransitSystem
Indicates that something is a component or segment within a larger transit or transportation system.
-
B.
rapidTransitSystem
Indicates a transportation relationship where people or goods are moved via a high-capacity, high-frequency public transit system designed for rapid travel over urban or regional routes.
-
C.
appliesToTransitSystem
Indicates that something (such as a rule, policy, feature, or condition) is relevant or applicable to a particular transit or transportation system.
-
D.
paratransitSystemName
Indicates the name assigned to a specific paratransit transportation system or service.
-
E.
railSystemType
chosen
Indicates the specific category or classification of a rail transportation system that an entity belongs to or operates within.
- 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_69ad85d6dc3c8190b491b79b83e25461 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc102cb2881908fa4dc1bf6fa5961 |
completed | March 8, 2026, 6:33 p.m. |
| PD | Predicate disambiguation | batch_69adb83810c481909c645c08b978edc1 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:21 p.m.