Triple
T10246897
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NM-02 |
E240238
|
entity |
| Predicate | usedOnLine |
P15252
|
FINISHED |
| Object | Metro Line 3 |
E47977
|
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: Metro Line 3 | Statement: [NM-02, usedOnLine, Metro Line 3]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Metro Line 3 Context triple: [NM-02, usedOnLine, Metro Line 3]
-
A.
Metro Line 3
chosen
Metro Line 3 is a major Mexico City Metro route that runs north–south across the city, connecting key residential and commercial areas including the Gustavo A. Madero borough.
-
B.
Metro Line 4
Metro Line 4 is a rapid transit route within a city's metro system that connects with other lines, including Metro Line 6, to facilitate passenger transfers across the network.
-
C.
Metro Line 5
Metro Line 5 is a rapid transit route within a city's metro system that connects with Metro Line 6 at one or more interchange stations.
-
D.
MRT Line 3
MRT Line 3 is a major elevated rapid transit line in Metro Manila that runs along EDSA, serving as one of the region’s primary commuter rail corridors.
-
E.
Metro Line 7
Metro Line 7 is a rapid transit route in a metropolitan subway network that connects multiple key districts and serves as an interchange point with several other lines.
- 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_69d381a7e198819090280d5ab885d59e |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d22cfe1c8190afae178e11a59b8b |
completed | April 7, 2026, 9:45 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d6f7a597188190880200d13784f18f |
completed | April 9, 2026, 12:49 a.m. |
Created at: April 6, 2026, 11:27 a.m.