Triple
T38681680
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VOT |
E943905
|
entity |
| Predicate | associatedWithNetworkAbbreviation |
P114068
|
FINISHED |
| Object | U-Bahn Wien |
E939191
|
NE 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: U-Bahn Wien | Statement: [VOT, associatedWithNetworkAbbreviation, U-Bahn Wien]
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 (4 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_69f76eec28708190b9c82a505fc278e0 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a43e9d27fac81908fd32871b041d3a1 |
completed | June 30, 2026, 4:07 p.m. |
| PD | Predicate disambiguation | batch_6a037a2026248190b894436a578d79ac |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:33 p.m.