Triple
T1561006
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oslofjord |
E33322
|
entity |
| Predicate | adjacentToCity |
P5707
|
FINISHED |
| Object | Drammen |
E105261
|
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: Drammen | Statement: [Oslofjord, adjacentToCity, Drammen]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Drammen Context triple: [Oslofjord, adjacentToCity, Drammen]
-
A.
Drammen
chosen
Drammen is a city and municipality in southeastern Norway known for its riverside setting along the Drammenselva and its role as a regional commercial and transport hub.
-
B.
Bærum
Bærum is a wealthy suburban municipality just west of Oslo, Norway, known for its high standard of living and residential communities.
-
C.
Gjøvik
Gjøvik is a town and municipality in Innlandet county, Norway, known for its location along Lake Mjøsa and its mix of industrial heritage and modern sports and cultural facilities.
-
D.
Sinsen
Sinsen is a neighborhood and major transport hub in Oslo, Norway, known for its busy traffic interchange and public transit connections.
-
E.
Ullensaker
Ullensaker is a municipality in Viken county, Norway, best known for hosting Oslo Airport, Gardermoen, the country’s main international airport.
- 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_69a885ef9cf48190b0af0f5ce3d02231 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a9088710a881909a1226e4b54311b8 |
completed | March 5, 2026, 4:37 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69adeac0be308190a12ba8e79589dead |
completed | March 8, 2026, 9:31 p.m. |
Created at: March 4, 2026, 7:27 p.m.