Triple
T20114267
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Strømsø |
E490412
|
entity |
| Predicate | hasNearbyDistrict |
P4647
|
FINISHED |
| Object | Bragernes |
—
|
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: Bragernes | Statement: [Strømsø, hasNearbyDistrict, Bragernes]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bragernes Context triple: [Strømsø, hasNearbyDistrict, Bragernes]
-
A.
Bragernes
chosen
Bragernes is a historic former town and district that now forms the northern part of the city of Drammen in Norway.
-
B.
Solbjerg
Solbjerg is a suburban town and residential area in the southern part of Aarhus, Denmark.
-
C.
Blangsted
Blangsted is a surname most notably associated with Folmar Blangsted, a film editor.
-
D.
Egeskov
Egeskov is a village on the island of Funen in Denmark best known for the nearby Renaissance water castle Egeskov Castle, one of Europe’s best-preserved moated castles.
-
E.
Vildbjerg
Vildbjerg is a Danish town that serves as the administrative center of the former Trehøje Municipality in the Central Denmark Region.
- 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_69da62636cc08190982cc71733a17b8d |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e666e31af081908d8e0c867c388a73 |
completed | April 20, 2026, 5:48 p.m. |
Created at: April 11, 2026, 11:29 p.m.