Triple
T13493685
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Foxton Locks |
E320704
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Foxton |
E290330
|
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: Foxton | Statement: [Foxton Locks, locatedNear, Foxton]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Foxton Context triple: [Foxton Locks, locatedNear, Foxton]
-
A.
Foxton
Foxton is a small village and civil parish in South Cambridgeshire, England, known for its rural character and proximity to Cambridge.
-
B.
Foxton
chosen
Foxton is a small coastal town in New Zealand known for its historic flax industry and proximity to the Manawatū River.
-
C.
Farlington
Farlington is a small rural village in North Yorkshire, England, situated near the River Foss and known for its historic parish church and agricultural surroundings.
-
D.
Farlington
Farlington is a residential suburb in the northern part of Portsmouth, England, known for its coastal location and access to major transport routes.
-
E.
Fordsburg
Fordsburg is a historic, culturally diverse suburb of Johannesburg known for its strong Indian and Muslim community, bustling markets, and vibrant street life.
- 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_69d807629d6c8190998f1b9bb12d2ed0 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbaf4da2c88190a867b53529d39545 |
completed | April 12, 2026, 2:42 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f7463d3a948190aab07a25fd903d4e |
completed | May 3, 2026, 12:57 p.m. |
Created at: April 9, 2026, 9:43 p.m.