Triple
T7294869
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Closeburn Castle |
E164493
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Closeburn |
E143351
|
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: Closeburn | Statement: [Closeburn Castle, locatedIn, Closeburn]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Closeburn Context triple: [Closeburn Castle, locatedIn, Closeburn]
-
A.
Closeburn
chosen
Closeburn is a historic area in Dumfries and Galloway, Scotland, traditionally associated with the lands of Clan Kirkpatrick.
-
B.
Mill Burn
Mill Burn is a small tributary stream in West Dunbartonshire, Scotland, that feeds into the River Leven.
-
C.
Burnsall
Burnsall is a picturesque village in North Yorkshire, England, known for its stone bridge, riverside setting, and traditional Dales scenery.
-
D.
Stoneyburn
Stoneyburn is a small village in West Lothian, Scotland, known historically for its coal mining roots and close-knit community.
-
E.
Brox Burn
Brox Burn is a small watercourse in West Lothian, Scotland, that flows through the town of Broxburn before joining the River Almond.
- 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_69c6887a499881909dd23341399c59d8 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6eb8b7cc08190983739bf667057c9 |
completed | March 27, 2026, 8:41 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c7e543c22c8190acf8dcffd9c59520 |
completed | March 28, 2026, 2:27 p.m. |
Created at: March 27, 2026, 3 p.m.