Triple
T14686770
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East Hills railway station |
E344927
|
entity |
| Predicate | servedByLine |
P1293
|
FINISHED |
| Object | T8 line |
E1090973
|
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: T8 line | Statement: [East Hills railway station, servedByLine, T8 line]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: T8 line Context triple: [East Hills railway station, servedByLine, T8 line]
-
A.
T8 Line
chosen
The T8 Line is a Sydney Trains suburban rail service that runs between the city and southwestern suburbs, including stations such as Minto.
-
B.
S8 line
The S8 line is a route of the Rhine-Main S-Bahn network in the Frankfurt region, providing suburban rail service that connects central Frankfurt with surrounding cities and the airport.
-
C.
S8 line
The S8 line is a regional commuter rail service within the Zürich S-Bahn network that connects the city of Zürich with surrounding suburbs and towns.
-
D.
S8 line
The S8 line is a Berlin S-Bahn route that runs across the city, connecting northern and southeastern districts via central transfer hubs.
-
E.
S8 Line
The S8 Line is a suburban rapid transit line of the Nanjing Metro system in Nanjing, China.
- 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_69d822e34b348190ada4d1cdb6c7c226 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb58306548190b981956a83a84b95 |
completed | April 14, 2026, 9:45 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fdf080b7508190ac99b8bb6cfb1881 |
completed | May 8, 2026, 2:17 p.m. |
Created at: April 10, 2026, 1:28 a.m.