Triple
T2976868
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yell Sound |
E80418
|
entity |
| Predicate | hasNearbySettlement |
P4647
|
FINISHED |
| Object | Ulsta |
E316479
|
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: Ulsta | Statement: [Yell Sound, hasNearbySettlement, Ulsta]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ulsta Context triple: [Yell Sound, hasNearbySettlement, Ulsta]
-
A.
Ulsta
chosen
Ulsta is a small settlement on the island of Yell in Shetland, Scotland, known primarily for its ferry terminal linking Yell to the Shetland mainland.
-
B.
Bekkestua
Bekkestua is a suburban center in Bærum, Norway, functioning as a local commercial and transport hub just west of Oslo.
-
C.
Thamerdal
Thamerdal is a residential neighborhood within the Dutch town of Uithoorn in the province of North Holland.
-
D.
Bergshamra
Bergshamra is a residential district in the northern Stockholm urban area of Sweden, known for its proximity to green spaces and good public transport connections.
-
E.
Solbo
Solbo is a locality within Botkyrka Municipality in Stockholm County, Sweden.
- 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_69ad8b15f6ac8190be5fd16a33edcb4f |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad998c589c8190b4530f3fb8975187 |
completed | March 8, 2026, 3:45 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b12e2c498881909dc0349b56db5c87 |
completed | March 11, 2026, 8:56 a.m. |
Created at: March 8, 2026, 2:58 p.m.