Triple
T3220441
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Copenhagen Metro |
E67498
|
entity |
| Predicate | lineName |
P28725
|
FINISHED |
| Object | M3 |
E338239
|
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: M3 | Statement: [Copenhagen Metro, lineName, M3]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: M3 Context triple: [Copenhagen Metro, lineName, M3]
-
A.
M3
M3 is a major motorway in the United Kingdom that connects London to Southampton, serving as a key route through southern England.
-
B.
M3
M3 is a boat line that operates as part of Geneva’s public transport network, providing passenger service across the city’s lake or waterways.
-
C.
M3
chosen
M3 is a circular line of the Copenhagen Metro that loops around the city center, connecting key districts and interchange stations.
-
D.
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.
-
E.
M2
M2 was the original name of MTV2, a U.S. cable television channel that focused on music videos and youth-oriented programming.
- 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_69ad858b8adc8190ad989712c87a476b |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69adae16f20081909d7f3bac016f961d |
completed | March 8, 2026, 5:12 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b2771be134819081809b2351517fdf |
completed | March 12, 2026, 8:19 a.m. |
Created at: March 8, 2026, 3:08 p.m.