Triple
T13345707
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wellswood |
E317943
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Torquay |
E80572
|
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: Torquay | Statement: [Wellswood, locatedIn, Torquay]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Torquay Context triple: [Wellswood, locatedIn, Torquay]
-
A.
Torquay
chosen
Torquay is a seaside resort town on the English Riviera in Devon, England, known for its mild climate, beaches, and Victorian-era tourism.
-
B.
Torquay
Torquay is a coastal suburb of Hervey Bay in Queensland, Australia, known for its beaches and tourism amenities.
-
C.
Paignton
Paignton is a seaside town in Devon, England, known for its sandy beaches, traditional pier, and role as part of the English Riviera resort area.
-
D.
Torbay
Torbay is a coastal unitary authority and popular seaside resort area in Devon, England, encompassing the towns of Torquay, Paignton, and Brixham.
-
E.
Brixham
Brixham is a historic fishing town and port in Devon, England, known for its maritime heritage and role in traditional shipbuilding.
- 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_69d806b5a3c08190b42c267fb092f98a |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99e89c65c819093f3bea11d6073c5 |
completed | April 11, 2026, 1:06 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fe0ccb9c3481908820f7620102e373 |
completed | May 8, 2026, 4:18 p.m. |
Created at: April 9, 2026, 9:31 p.m.