Triple
T17370768
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Randsfjord Line |
E422306
|
entity |
| Predicate | terminus |
P388
|
FINISHED |
| Object | Drammen |
—
|
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: Drammen | Statement: [Randsfjord Line, terminus, Drammen]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Drammen Context triple: [Randsfjord Line, terminus, 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.
Røa
Røa is a residential neighborhood in the western part of Oslo, Norway, known for its green surroundings and good public transport connections.
-
C.
Slemdal
Slemdal is a residential neighborhood in the Vestre Aker borough of Oslo, Norway, known for its green surroundings and affluent character.
-
D.
Smestad
Smestad is a residential neighborhood in Oslo, Norway, known for its affluent housing and proximity to green areas and good public transport.
-
E.
Sokna
Sokna is an extinct Eastern Berber language formerly spoken around the oasis town of Sokna in central Libya.
- 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_69d889d6535c81908be333c01deaec4e |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43a68ff448190b505861e56df5b6d |
completed | April 19, 2026, 2:14 a.m. |
Created at: April 10, 2026, 5:44 a.m.