Triple
T15827866
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Piața Victoriei metro station |
E383790
|
entity |
| Predicate | hasLine |
P35
|
FINISHED |
| Object | M2 |
E1163588
|
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: M2 | Statement: [Piața Victoriei metro station, hasLine, M2]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: M2 Context triple: [Piața Victoriei metro station, hasLine, M2]
-
A.
M2
M2 is a major British motorway that connects London with the port town of Dover in Kent, serving as an important route to the Channel ports.
-
B.
M2
M2 was the original name of MTV2, a U.S. cable television channel that focused on music videos and youth-oriented programming.
-
C.
M2
chosen
M2 is one of the main lines of the Budapest Metro, running east–west across the city and connecting several key transport hubs.
-
D.
M2
M2 is a boat line that operates as part of Geneva’s public transport network, providing passenger services across the city’s waters.
-
E.
M2
M2 is a central Manchester, England postcode district covering part of the city’s main commercial and business area.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d86da34c888190976e06c4019d415a |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e11e61c7508190ba1f675f2092364c |
completed | April 16, 2026, 5:37 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff999da5008190921b3f129787999e |
completed | May 9, 2026, 8:31 p.m. |
Created at: April 10, 2026, 4:49 a.m.