Triple
T21478545
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Karachi–Peshawar Railway Line |
E529925
|
entity |
| Predicate | alsoKnownAs |
P39
|
FINISHED |
| Object | ML-1 |
—
|
NE NERFINISHED |
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: ML-1 | Statement: [Karachi–Peshawar Railway Line, alsoKnownAs, ML-1]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: ML-1 Context triple: [Karachi–Peshawar Railway Line, alsoKnownAs, ML-1]
-
A.
ML-1
chosen
ML-1 is Pakistan Railways’ primary north–south main line, connecting major cities and serving as the backbone of the country’s rail transport system.
-
B.
ML-2
ML-2 is a major north–south railway corridor in Pakistan that serves as one of the country’s principal main lines parallel to the primary ML-1 route.
-
C.
ML-3
ML-3 is one of Pakistan Railways’ main railway corridors, serving as a key route that supports regional connectivity and freight and passenger movement within the country.
-
D.
ML10
ML10 is a postcode district within the ML (Motherwell) postcode area in central Scotland, covering Strathaven and surrounding settlements.
-
E.
ML3
ML3 is a UK postcode district covering part of Hamilton and surrounding areas in South Lanarkshire, Scotland.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0c45acc3881908e38d3f28964152b |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9ea1951fc8190910f634327aa5c3f |
completed | April 23, 2026, 9:44 a.m. |
Created at: April 16, 2026, 6:20 p.m.