Triple
T17011523
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M1 line |
E412710
|
entity |
| Predicate | hasRouteNumber |
P1864
|
FINISHED |
| Object | M1 |
unclear NED1
|
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: M1 | Statement: [M1 line, hasRouteNumber, M1]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: M1 Context triple: [M1 line, hasRouteNumber, M1]
-
A.
M1
M1 is the first and primary north–south metro line of the Warsaw Metro system in Poland.
-
B.
M1
M1 is one of the main lines of the Copenhagen Metro, providing rapid transit service through central Copenhagen and connecting key residential and commercial areas.
-
C.
M1
M1 is a major north–south urban freeway in Johannesburg, South Africa, connecting the city center with key suburbs and routes.
-
D.
M1
M1 is the main primary mirror of the Extremely Large Telescope, responsible for collecting and focusing incoming light for its observations.
-
E.
M1
M1 is a major Irish motorway that connects Dublin to the border with Northern Ireland, forming part of the primary route between the Republic of Ireland and Belfast.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide. chosen
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_69d886cc4170819093deddc7b8b4b6a7 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d47cc17c819087f7bd27582bcbfa |
completed | April 18, 2026, 6:59 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a011b46e89c81908271eb22b535c558 |
completed | May 10, 2026, 11:56 p.m. |
Created at: April 10, 2026, 5:33 a.m.