Triple
T20707318
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Norwegian National Road 35 |
E508938
|
entity |
| Predicate | connects |
P390
|
FINISHED |
| Object | Gardermoen |
—
|
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: Gardermoen | Statement: [Norwegian National Road 35, connects, Gardermoen]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gardermoen Context triple: [Norwegian National Road 35, connects, Gardermoen]
-
A.
Gardermoen
chosen
Gardermoen is a major Norwegian air base and aviation hub that has historically served as an important military airfield for Norway.
-
B.
Gardermoen (Vestby)
Gardermoen (Vestby) is a small village in Vestby Municipality in Viken county, Norway.
-
C.
Oslo TMA
Oslo TMA is a controlled terminal maneuvering area of Norwegian airspace surrounding Oslo, managing arriving and departing air traffic for the region’s main airports.
-
D.
Oslo
Oslo is the capital and largest city of Norway, known as a major cultural, economic, and governmental center.
-
E.
Oslo
Oslo is a collection of shared libraries that provide common code and patterns used across various OpenStack projects.
- 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_69e0b4c40ad88190b81f77695366d328 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c1917ce08190a54720d4d5b0a02c |
completed | April 21, 2026, 12:15 a.m. |
Created at: April 16, 2026, 12:14 p.m.