Triple
T22761436
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Commando Logistic Regiment |
E562999
|
entity |
| Predicate | basedNear |
P350
|
FINISHED |
| Object | Barnstaple, Devon |
—
|
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: Barnstaple, Devon | Statement: [Commando Logistic Regiment, basedNear, Barnstaple, Devon]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Barnstaple, Devon Context triple: [Commando Logistic Regiment, basedNear, Barnstaple, Devon]
-
A.
Barnstaple, Devon, England
Barnstaple, Devon, England is a historic market and river-port town in North Devon known as one of the oldest boroughs in the United Kingdom.
-
B.
Barnstaple
chosen
Barnstaple is a historic market town in North Devon, England, known as one of the region’s main commercial and service centers.
-
C.
Bideford
Bideford is a historic port town on the River Torridge in North Devon, England, known for its maritime heritage and role as a local commercial center.
-
D.
Bideford
Bideford is a small rural settlement in the Carterton District of New Zealand’s Wairarapa region.
-
E.
Bridgwater
Bridgwater is a historic market town in Somerset, England, known for its maritime heritage and role in regional trade and industry.
- 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_69e24552e11c81909c2d61578a558bd7 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17a7c45b881908b29ba1439038789 |
completed | April 29, 2026, 3:26 a.m. |
Created at: April 17, 2026, 3:26 p.m.