Triple
T2948991
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southern Scotland |
E79571
|
entity |
| Predicate | hasSettlement |
P1068
|
FINISHED |
| Object | Langholm |
E304724
|
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: Langholm | Statement: [Southern Scotland, hasSettlement, Langholm]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Langholm Context triple: [Southern Scotland, hasSettlement, Langholm]
-
A.
Langholm
chosen
Langholm is a small town in the Scottish Borders known historically for its textile industry and scenic position in the valley of the River Esk.
-
B.
Kinglassie
Kinglassie is a small village in Fife, Scotland, known historically for its coal mining heritage and rural character.
-
C.
Moodiesburn
Moodiesburn is a suburban village in North Lanarkshire, Scotland, situated to the northeast of Glasgow and largely serving as a commuter community.
-
D.
Longniddry
Longniddry is a coastal village in Scotland known for its sandy beach, golf course, and role as a commuter settlement for nearby Edinburgh.
-
E.
Ilkeston
Ilkeston is a market town in the East Midlands of England, historically known for its coal mining and textile industries.
- 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_69ad8b1089588190b74d9e2505e45762 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad98b6cab88190b4dee7e5ec9347e5 |
completed | March 8, 2026, 3:41 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b0869732d08190bdb6f6c76411ade1 |
completed | March 10, 2026, 9:01 p.m. |
Created at: March 8, 2026, 2:57 p.m.