Triple
T7635213
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Addiewell |
E172859
|
entity |
| Predicate | hasNearbySettlement |
P4647
|
FINISHED |
| Object | Loganlea |
E663572
|
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: Loganlea | Statement: [Addiewell, hasNearbySettlement, Loganlea]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Loganlea Context triple: [Addiewell, hasNearbySettlement, Loganlea]
-
A.
Loganlea
chosen
Loganlea is a small settlement in West Lothian, Scotland, situated near Addiewell and served by the nearby Addiewell railway station.
-
B.
Kiloran
Kiloran is a small coastal settlement on the Scottish island of Colonsay, known for its scenic bay and sandy beach.
-
C.
Sholto
Sholto is a masculine given name of Scottish origin, historically associated with figures such as military leaders and nobles.
-
D.
Leagrave
Leagrave is a suburban area of Luton in Bedfordshire, England, known as the district where the River Lea originates.
-
E.
Kilgetty
Kilgetty is a small village in Pembrokeshire, Wales, known as a local residential and service hub near the coastal resort of Saundersfoot.
- 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_69c69952849881908fdcea7a93bfc307 |
completed | March 27, 2026, 2:50 p.m. |
| NER | Named-entity recognition | batch_69c6faa83fcc8190a3f0bb20cbe1b2d6 |
completed | March 27, 2026, 9:46 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c870c33ce081908df916d769fa84be |
completed | March 29, 2026, 12:22 a.m. |
Created at: March 27, 2026, 3:57 p.m.