Triple
T20306049
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Söderbysjön |
E505610
|
entity |
| Predicate | hasEtymology |
P453
|
FINISHED |
| Object | named after nearby settlement Söderby |
—
|
NE NERFINISHED |
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: named after nearby settlement Söderby | Statement: [Söderbysjön, hasEtymology, named after nearby settlement Söderby]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: named after nearby settlement Söderby Context triple: [Söderbysjön, hasEtymology, named after nearby settlement Söderby]
-
A.
Söderby
chosen
Söderby is a small village located within the Pellinge archipelago in southern Finland, known for its coastal scenery and traditional island life.
-
B.
Stureby
Stureby is a residential district in southern Stockholm, Sweden, known for its suburban character and local amenities.
-
C.
Enebyberg
Enebyberg is a residential suburban area in the northern part of the Stockholm urban region in Sweden.
-
D.
Melmerby
Melmerby is a small rural village located in the Coverdale area of the Yorkshire Dales in North Yorkshire, England.
-
E.
Sundby
Sundby is a district on the island of Amager in Copenhagen, Denmark, encompassing the neighborhoods of Sundbyvester and Sundbyøster.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0b4b8ab648190906e18538c250148 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6773f8f688190b616f972b9bbb28e |
completed | April 20, 2026, 6:58 p.m. |
Created at: April 16, 2026, 11:18 a.m.