Triple
T19155348
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bromma |
E468914
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Nockeby |
—
|
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: Nockeby | Statement: [Bromma, contains, Nockeby]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Nockeby Context triple: [Bromma, contains, Nockeby]
-
A.
Nockeby
chosen
Nockeby is a residential district in western Stockholm, Sweden, known as the terminus of one of the city's historic tram lines.
-
B.
Fulletby
Fulletby is a small rural village in Lincolnshire, England, situated in the scenic Lincolnshire Wolds.
-
C.
Skegby
Skegby is a village and former mining community in Nottinghamshire, England, situated near the town of Sutton-in-Ashfield.
-
D.
Knudshoved
Knudshoved is a coastal area on the Danish island of Funen that serves as a key transport hub and former ferry terminal at the western end of the Great Belt crossing.
-
E.
Nesseby
Nesseby is a small coastal municipality in Troms og Finnmark county in northern Norway, known for its Sámi culture and location along the Varangerfjorden.
- 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_69d8dd084ff48190ac0f8c46ee722629 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5eeb914248190a92dc5f30cbc8fcc |
completed | April 20, 2026, 9:15 a.m. |
Created at: April 10, 2026, 12:06 p.m.