Triple
T3339611
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Angus council area |
E70224
|
entity |
| Predicate | containsVillage |
P4011
|
FINISHED |
| Object | Kirkton of Menmuir |
E349111
|
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: Kirkton of Menmuir | Statement: [Angus council area, containsVillage, Kirkton of Menmuir]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kirkton of Menmuir Context triple: [Angus council area, containsVillage, Kirkton of Menmuir]
-
A.
Kirkbuddo
Kirkbuddo is a small rural village in eastern Scotland, situated within the historic county of Angus.
-
B.
Menmuir
chosen
Menmuir is a small rural village in eastern Scotland, known for its agricultural landscape and historic parish setting within the Angus region.
-
C.
Kirkton of Kingoldrum
Kirkton of Kingoldrum is a small rural village in the Scottish county of Angus.
-
D.
Kingussie
Kingussie is a small town in the Scottish Highlands that serves as a local hub and rail stop on the route between Edinburgh and Inverness.
-
E.
Kirkton
Kirkton is a small settlement located within West Lothian in central Scotland.
- 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_69ad85a405e48190b6e68de7cf9f319e |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb1bf1f648190993ac8e9dda60983 |
completed | March 8, 2026, 5:28 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b33426f73881908eb0759c47eb08d7 |
completed | March 12, 2026, 9:46 p.m. |
Created at: March 8, 2026, 3:12 p.m.