Triple
T17345498
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Glen Devon |
E421675
|
entity |
| Predicate | near |
P350
|
FINISHED |
| Object | Glendevon |
E612965
|
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: Glendevon | Statement: [Glen Devon, near, Glendevon]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Glendevon Context triple: [Glen Devon, near, Glendevon]
-
A.
Glendevon
chosen
Glendevon is a small village in Perth and Kinross, Scotland, situated in a scenic glen known for its river, reservoirs, and surrounding hills.
-
B.
Weston Rhyn
Weston Rhyn is a small village in Shropshire, England, situated near the Welsh border and close to the town of Chirk.
-
C.
Gnosall
Gnosall is a large rural village and civil parish in Staffordshire, England, known for its historic canal, agricultural surroundings, and community amenities.
-
D.
Leintwardine
Leintwardine is a small historic village in Herefordshire, England, near the Welsh border, known for its Roman heritage and rural setting.
-
E.
Grindon
Grindon is a residential suburb of Sunderland in the Wearside area of North East England.
- 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_69d889d520008190a26917a95bf1c2ea |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43a286d34819080c5148c220fd5a1 |
completed | April 19, 2026, 2:12 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a018c5be49c8190b27a4fe1df8e8ab6 |
completed | May 11, 2026, 7:59 a.m. |
Created at: April 10, 2026, 5:44 a.m.