Triple
T4367720
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aurillac |
E98817
|
entity |
| Predicate | twinTown |
P1072
|
FINISHED |
| Object | Bideford |
E174028
|
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: Bideford | Statement: [Aurillac, twinTown, Bideford]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bideford Context triple: [Aurillac, twinTown, Bideford]
-
A.
Bideford
chosen
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.
-
B.
Bridgwater
Bridgwater is a historic market town in Somerset, England, known for its maritime heritage and role in regional trade and industry.
-
C.
Barnstaple
Barnstaple is a historic market town in North Devon, England, known as one of the region’s main commercial and service centers.
-
D.
Bridport
Bridport is a historic market town in southwest England known for its rope-making heritage and proximity to the Jurassic Coast.
-
E.
Poole
Poole is a coastal town and seaport in Dorset, England, known for its large natural harbour and maritime activities.
- 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_69b3454db3708190aeafd814413c4c3d |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b35201be7081908808e81634060f95 |
completed | March 12, 2026, 11:53 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b5dbcec90881908fe83c83119d99fe |
completed | March 14, 2026, 10:06 p.m. |
Created at: March 12, 2026, 11:17 p.m.