Triple
T19740837
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hawthorne station |
E474111
|
entity |
| Predicate | formerName |
P65
|
FINISHED |
| Object | Unionville |
—
|
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: Unionville | Statement: [Hawthorne station, formerName, Unionville]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Unionville Context triple: [Hawthorne station, formerName, Unionville]
-
A.
Unionville
chosen
Unionville was the former name of Hawthorne, a hamlet in the town of Mount Pleasant in Westchester County, New York.
-
B.
Olinville
Olinville is a residential neighborhood in the north-central Bronx in New York City, characterized by its mix of apartment buildings and one- to two-family homes.
-
C.
Reesville
Reesville is a rural locality in the Sunshine Coast hinterland of Queensland, Australia, known for its scenic countryside and proximity to water catchment areas.
-
D.
Stewarttown
Stewarttown is a small community located within the town of Halton Hills in Ontario, Canada.
-
E.
Yatesville
Yatesville is a small town located in the U.S. state of Georgia.
- 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_69d8e517ebd48190979ee76723bcfadf |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6516159c8819090022094aa91902b |
completed | April 20, 2026, 4:16 p.m. |
Created at: April 10, 2026, 1:47 p.m.