Triple
T21374272
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lysaker |
E527154
|
entity |
| Predicate | hasBridge |
P386
|
FINISHED |
| Object | Lysaker Bridge |
—
|
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: Lysaker Bridge | Statement: [Lysaker, hasBridge, Lysaker Bridge]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lysaker Bridge Context triple: [Lysaker, hasBridge, Lysaker Bridge]
-
A.
Lysaker Bridge
chosen
Lysaker Bridge is a key road and rail bridge in the Oslo area of Norway, carrying major traffic across the Lysaker River between Oslo and Bærum.
-
B.
Drammen Bridge
Drammen Bridge is a major road bridge in Drammen, Norway, carrying traffic across the Drammenselva river and connecting key parts of the city.
-
C.
Sandvika Bridge
Sandvika Bridge is a notable road bridge in the town of Sandvika, Norway, serving as an important local crossing and traffic connection.
-
D.
Kongsvinger Bridge
Kongsvinger Bridge is a road bridge in Kongsvinger, Norway, spanning the Glomma River and serving as a key local crossing visible from the historic Kongsvinger Fortress.
-
E.
Porsgrunn Bridge
Porsgrunn Bridge is a road bridge in Porsgrunn, Norway, that spans the Porsgrunn River and connects key parts of the town’s urban area.
- 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_69e0b51e80808190ba5cb05667af02a9 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e8b0b3666c8190a83bb32eeba24105 |
completed | April 22, 2026, 11:27 a.m. |
Created at: April 16, 2026, 5:10 p.m.