Triple
T14830878
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMS Terror |
E348698
|
entity |
| Predicate | builtAt |
P283
|
FINISHED |
| Object | Topsham |
E1038314
|
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: Topsham | Statement: [HMS Terror, builtAt, Topsham]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Topsham Context triple: [HMS Terror, builtAt, Topsham]
-
A.
Topsham
chosen
Topsham is a historic estuary town in Devon, England, known for its maritime heritage, Dutch-influenced architecture, and position on the River Exe near Exeter.
-
B.
Betsham
Betsham is a small village in Kent, England, situated within the DA (Dartford) postcode area.
-
C.
Garboldisham
Garboldisham is a village and civil parish in Norfolk, England, known for its historic country house Garboldisham Hall and rural setting.
-
D.
Thakeham
Thakeham is a rural village and civil parish in West Sussex, England, known for its historic buildings and countryside setting within the Horsham District.
-
E.
Thankerton
Thankerton is a small village in South Lanarkshire, Scotland, situated within the historic district of Clydesdale.
- 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_69d822ec69008190a9232caa68836872 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69ded0748eec8190a39c94024c3a3e3e |
completed | April 14, 2026, 11:40 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fe38a16fd881909d246d8d1811a673 |
completed | May 8, 2026, 7:25 p.m. |
Created at: April 10, 2026, 1:52 a.m.