Triple
T15865900
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lieutenancy area of Shetland |
E384712
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Fetlar |
E26067
|
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: Fetlar | Statement: [Lieutenancy area of Shetland, contains, Fetlar]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Fetlar Context triple: [Lieutenancy area of Shetland, contains, Fetlar]
-
A.
Fetlar
chosen
Fetlar is one of the Shetland Islands in Scotland, known for its rich birdlife and rural landscapes.
-
B.
Graemsay
Graemsay is a small inhabited island in the Orkney archipelago of Scotland, known for its lighthouses and rural landscape.
-
C.
Luskentyre
Luskentyre is a scenic coastal area on the Isle of Harris in Scotland, renowned for its expansive white-sand beaches and turquoise waters.
-
D.
Assynt
Assynt is a remote, rugged region in northwest Scotland known for its dramatic landscapes and as a notable site of the Highland Clearances.
-
E.
Rothiesholm
Rothiesholm is a small settlement on the Orkney island of Stronsay in 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_69d86da4e86481909f1325fdc971b5ec |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e1555f75e88190bfd0f551d4ccf4cc |
completed | April 16, 2026, 9:32 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffa947ba3881909c602f2fc60dd6e8 |
completed | May 9, 2026, 9:38 p.m. |
Created at: April 10, 2026, 4:50 a.m.