Triple
T13233003
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tor Bay |
E315069
|
entity |
| Predicate | hasShore |
P969
|
FINISHED |
| Object | Paignton |
E553667
|
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: Paignton | Statement: [Tor Bay, hasShore, Paignton]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Paignton Context triple: [Tor Bay, hasShore, Paignton]
-
A.
Paignton
chosen
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.
-
B.
Torquay
Torquay is a coastal suburb of Hervey Bay in Queensland, Australia, known for its beaches and tourism amenities.
-
C.
Torquay
Torquay is a seaside resort town on the English Riviera in Devon, England, known for its mild climate, beaches, and Victorian-era tourism.
-
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.
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_69d806affc688190a25b6ccc588e9c72 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98d34ff288190bdb550a019b7a470 |
completed | April 10, 2026, 11:52 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f72664b9a48190a76e0c3dfaaf3d7a |
completed | May 3, 2026, 10:41 a.m. |
Created at: April 9, 2026, 9:22 p.m.