Triple
T14346911
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hornsby railway station |
E355747
|
entity |
| Predicate | serves |
P98
|
FINISHED |
| Object | Hornsby |
E355747
|
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: Hornsby | Statement: [Hornsby railway station, serves, Hornsby]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hornsby Context triple: [Hornsby railway station, serves, Hornsby]
-
A.
Hornsby
chosen
Hornsby is a major residential and commercial suburb in northern Sydney, New South Wales, known for its busy shopping precinct and transport hub.
-
B.
Hornsby
Hornsby is a surname most famously associated with Rogers Hornsby, one of Major League Baseball’s greatest hitters.
-
C.
Kurrajong
Kurrajong is a locality in the Australian Capital Territory known for its rural character and proximity to the Ginninderra region.
-
D.
Kurrajong
Kurrajong is an electorate of the Australian Capital Territory Legislative Assembly that covers central Canberra and surrounding suburbs.
-
E.
Casula
Casula is a suburb in south-western Sydney, New South Wales, Australia, known as a residential area with transport links including its local railway station.
- 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_69d82790a7e08190877e2d349b2e8d8e |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de8e8b81bc8190ace2a575faf55cc0 |
completed | April 14, 2026, 6:59 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd4c4145c081909832e2334a064fb0 |
completed | May 8, 2026, 2:36 a.m. |
Created at: April 10, 2026, 1:14 a.m.