Triple
T14147527
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sydney–Newcastle rail corridor |
E350591
|
entity |
| Predicate | terminus |
P388
|
FINISHED |
| Object | Newcastle |
E83982
|
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: Newcastle | Statement: [Sydney–Newcastle rail corridor, terminus, Newcastle]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Newcastle Context triple: [Sydney–Newcastle rail corridor, terminus, Newcastle]
-
A.
Newcastle
Newcastle is a settlement within the Parish of St. Andrew, likely a small town or village in a predominantly rural Caribbean island parish.
-
B.
Newcastle
chosen
Newcastle is a coastal city in New South Wales, Australia, known for its busy port, beaches, and industrial heritage.
-
C.
Newcastle
Newcastle is a community in the municipality of Clarington, Ontario, known for its small-town character and location along the north shore of Lake Ontario.
-
D.
Newcastle
Newcastle is a small suburban village in South Dublin, Ireland, known for its historic character and proximity to Dublin city.
-
E.
Newcastle
Newcastle is a small unincorporated community located in Iron County, Utah, in the western United States.
- 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_69d827865f608190b311820428ae027b |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de612266248190a8591b646fe30ae6 |
completed | April 14, 2026, 3:45 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd19395924819084d78815c3f12f43 |
completed | May 7, 2026, 10:59 p.m. |
Created at: April 10, 2026, 12:54 a.m.