Triple
T38561736
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MVG |
E928093
|
entity |
| Predicate | operatesUrbanRailNetworkIn |
P148863
|
FINISHED |
| Object | Munich |
E21335
|
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: Munich | Statement: [MVG, operatesUrbanRailNetworkIn, Munich]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatesUrbanRailNetworkIn Context triple: [MVG, operatesUrbanRailNetworkIn, Munich]
-
A.
operatesRailNetworkOf
chosen
Indicates that one entity manages and runs the rail network belonging to or associated with another entity.
-
B.
operatesRailLinesOnIsland
Indicates that a railway operator runs or manages rail lines located on a specific island.
-
C.
operatedUndergroundRailway
Indicates that an entity managed or ran an underground railway system as an operator or controlling organization.
-
D.
hasRailTransportOperator
Indicates that a rail transport system, service, or infrastructure is operated or managed by a specified rail transport operator.
-
E.
operatesRegionalRailServices
Indicates that an entity manages and runs passenger rail transport services within a specific region or set of regions.
- 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_69f76eb8d1808190a588af29d8b266d6 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a4205afe5608190be177d39f22b233b |
completed | June 29, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_6a037a1e32108190897356d6a7fed879 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:32 p.m.