Triple
T7770717
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Metro Line 54 |
E179060
|
entity |
| Predicate | sharesTracksWith |
P5071
|
FINISHED |
| Object | Metro Line 53 |
E176815
|
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 53 | Statement: [Metro Line 54, sharesTracksWith, Metro Line 53]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Metro Line 53 Context triple: [Metro Line 54, sharesTracksWith, Metro Line 53]
-
A.
Metro Line 53
chosen
Metro Line 53 is a rapid transit line in Amsterdam that connects the city center with the southeastern suburbs as part of the Amsterdam Metro system.
-
B.
Metro Line 54
Metro Line 54 is a rapid transit line in the Amsterdam Metro system that connects the city center with southeastern suburbs such as Bijlmermeer.
-
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.
Metro line 51
Metro line 51 is a former hybrid metro/light rail line in Amsterdam that connected the city center with the southern suburbs, including Amsterdam Zuid.
-
E.
Metro line 52
Metro line 52 is Amsterdam’s North–South metro line, connecting the city’s northern and southern districts via the city center and major hubs like Amsterdam Zuid.
- 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_69c69f30602c819082ab52cd4af5c592 |
completed | March 27, 2026, 3:16 p.m. |
| NER | Named-entity recognition | batch_69c70438ca2481909114b0c434717109 |
completed | March 27, 2026, 10:27 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c8d6d0f1988190b4df650bebb61fd3 |
completed | March 29, 2026, 7:37 a.m. |
Created at: March 27, 2026, 4:11 p.m.