Triple
T21551068
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orcombe Point |
E531761
|
entity |
| Predicate | near |
P350
|
FINISHED |
| Object | Exmouth |
—
|
NE NERFINISHED |
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: Exmouth | Statement: [Orcombe Point, near, Exmouth]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Exmouth Context triple: [Orcombe Point, near, Exmouth]
-
A.
Exmouth
chosen
Exmouth is a coastal town in Devon, England, known as a popular seaside resort at the mouth of the River Exe.
-
B.
Exmouth
Exmouth is a remote coastal town in Western Australia known as the main gateway to the Ningaloo Reef, famous for its marine life and whale shark encounters.
-
C.
Brixham
Brixham is a historic fishing town and port in Devon, England, known for its maritime heritage and role in traditional shipbuilding.
-
D.
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.
-
E.
Torquay
Torquay is a seaside resort town on the English Riviera in Devon, England, known for its mild climate, beaches, and Victorian-era tourism.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0c460232c81908de2c3819d17c00e |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69eeb59258b88190966c18f1f519dad6 |
completed | April 27, 2026, 1:02 a.m. |
Created at: April 16, 2026, 6:29 p.m.