Triple
T38681680
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VOT |
E943905
|
entity |
| Predicate | associatedWithNetworkAbbreviation |
—
|
GENERATED |
| Object | U-Bahn Wien |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithNetworkAbbreviation Context triple: [VOT, associatedWithNetworkAbbreviation, U-Bahn Wien]
-
A.
usesCoreNetworkAbbreviation
Indicates that one entity refers to or represents another entity using an abbreviated form specific to a core network context.
-
B.
associatedNetworkType
Indicates a relationship where one entity is linked to or characterized by a particular type of network with which it is associated.
-
C.
associatedWithNetworkOfNotableBearer
Indicates that an entity is connected to or involved with a network or group formed around a notable bearer of a name, title, or role.
-
D.
associatedWithRouteNetwork
Indicates a relationship where something is linked or connected to a specific route network.
-
E.
hasNetworkName
chosen
Indicates that an entity is associated with a specific network identifier or name.
- F. None of above.
Provenance (1 batch)
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_69f76eec28708190b9c82a505fc278e0 |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:33 p.m.