Triple
T16118991
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sandown Raceway |
E391082
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Springvale |
E623205
|
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: Springvale | Statement: [Sandown Raceway, locatedNear, Springvale]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Springvale Context triple: [Sandown Raceway, locatedNear, Springvale]
-
A.
Springvale
Springvale is a small community located within Hamblen County in the state of Tennessee, United States.
-
B.
Springvale
chosen
Springvale is a suburb in Melbourne, Victoria, Australia, known for its cultural diversity and busy commercial and transport hub.
-
C.
Westvale
Westvale is a residential area in the town of Kirkby in Merseyside, England.
-
D.
Southville
Southville is an inner-city residential district of Bristol, England, known for its Victorian terraces, independent shops, and vibrant arts and café culture.
-
E.
Rivervale
Rivervale is an inner-eastern suburb of Perth, Western Australia, known for its residential areas, proximity to the Swan River, and easy access to the city centre.
- 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_69d87f1a8dd881909f1de6ef78849874 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e2016d527c8190928e73661b18a914 |
completed | April 17, 2026, 9:46 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fff2a61e448190be1f8c79cae6c7ee |
completed | May 10, 2026, 2:51 a.m. |
Created at: April 10, 2026, 5 a.m.