Triple
T15030381
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mörby centrum |
E378326
|
entity |
| Predicate | suburb |
P47577
|
FINISHED |
| Object | Mörby |
E507456
|
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: Mörby | Statement: [Mörby centrum, suburb, Mörby]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Mörby Context triple: [Mörby centrum, suburb, Mörby]
-
A.
Mörby
chosen
Mörby is a locality in the Stockholm area of Sweden served by a station on the Roslagsbanan narrow-gauge railway line.
-
B.
Mjölby
Mjölby is a small Swedish town known for its agricultural surroundings and location in the southern part of Östergötland County.
-
C.
Melmerby
Melmerby is a small rural village located in the Coverdale area of the Yorkshire Dales in North Yorkshire, England.
-
D.
Börje
Börje is a masculine given name of Swedish origin, notably borne by the legendary ice hockey player Börje Salming.
-
E.
Nyboder
Nyboder is a historic district in Copenhagen known for its distinctive 17th-century yellow terraced houses originally built to house Royal Danish Navy personnel.
- 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_69d85cd46b2c819090d054c27787f677 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded7e2416081908dfba48d7f7b4a84 |
completed | April 15, 2026, 12:12 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fe9ddb46888190b1d2fe2992fc120b |
completed | May 9, 2026, 2:37 a.m. |
Created at: April 10, 2026, 2:59 a.m.