Triple
T8910690
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ashford International railway station |
E212172
|
entity |
| Predicate | connectsTo |
P845
|
FINISHED |
| Object | Hastings |
E75945
|
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: Hastings | Statement: [Ashford International railway station, connectsTo, Hastings]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hastings Context triple: [Ashford International railway station, connectsTo, Hastings]
-
A.
Hastings
Hastings is a surname most prominently associated with Reed Hastings, the co-founder and longtime CEO of Netflix.
-
B.
Hastings
Hastings is a coastal town on Victoria, Australia’s Mornington Peninsula known for its port facilities and access to Western Port Bay.
-
C.
Hastings
Hastings is a small commuter rail stop in Weston, Massachusetts, served by the MBTA's Fitchburg Line.
-
D.
Hastings
Hastings is a small rural city located in Mills County in the southwestern part of the U.S. state of Iowa.
-
E.
Hastings
chosen
Hastings is a historic seaside town and popular coastal resort in East Sussex, England, best known for its association with the 1066 Battle of Hastings and its traditional fishing and tourism industries.
- 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_69ca839255248190b43984294abd92ae |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc65227d008190b13ba162d0b3c9d1 |
completed | April 1, 2026, 12:21 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cfba36f8cc8190ab57ddc99b7219d1 |
completed | April 3, 2026, 1:01 p.m. |
Created at: March 30, 2026, 6:55 p.m.