Triple
T13898733
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kingsbridge |
E334161
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Salcombe |
E788127
|
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: Salcombe | Statement: [Kingsbridge, locatedNear, Salcombe]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Salcombe Context triple: [Kingsbridge, locatedNear, Salcombe]
-
A.
Salcombe
chosen
Salcombe is a picturesque coastal town in South Devon, England, known for its sailing, sandy beaches, and scenic estuary setting.
-
B.
Salcombe Regis
Salcombe Regis is a small coastal village in Devon, England, known for its scenic countryside and proximity to the seaside town of Sidmouth.
-
C.
Nailsea
Nailsea is a small town in North Somerset, England, historically known for its glassmaking and coal mining industries.
-
D.
Teignmouth
Teignmouth is a seaside town on the south coast of Devon, England, known for its historic port, sandy beaches, and scenic coastal railway views.
-
E.
Yeovilton
Yeovilton is a village in Somerset, England, best known for its Royal Naval Air Station and strong association with British naval aviation.
- 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_69d81c5eaa9c819083b1ff8689179565 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de25d8897881908b770cdb565898d4 |
completed | April 14, 2026, 11:32 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fcf7d44d848190ab445833e64a6bfc |
completed | May 7, 2026, 8:36 p.m. |
Created at: April 9, 2026, 10:15 p.m.