Triple
T14150893
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roxburghshire |
E350674
|
entity |
| Predicate | containsVillage |
P4011
|
FINISHED |
| Object | Ancrum |
E1081842
|
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: Ancrum | Statement: [Roxburghshire, containsVillage, Ancrum]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ancrum Context triple: [Roxburghshire, containsVillage, Ancrum]
-
A.
Ancrum
chosen
Ancrum is a small village in the Scottish Borders region of Scotland, situated near the River Teviot and known for its historic rural character.
-
B.
Heamoor
Heamoor is a village in Cornwall, England, situated just outside the town of Penzance.
-
C.
Torphichen
Torphichen is a historic village in central Scotland known for its medieval preceptory of the Knights Hospitaller and its picturesque rural setting.
-
D.
Grindon
Grindon is a residential suburb of Sunderland in the Wearside area of North East England.
-
E.
Umberleigh
Umberleigh is a small rural village in North Devon, England, situated on the River Taw and served by a local railway station.
- 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_69d8278775fc8190b0802d22ca2f495d |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de6124e23481909e5132a40a1d8624 |
completed | April 14, 2026, 3:45 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fcf7e86820819099d6e3d3d4229f0d |
completed | May 7, 2026, 8:36 p.m. |
Created at: April 10, 2026, 12:57 a.m.