Triple
T26857752
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hålogaland Bridge |
E676240
|
entity |
| Predicate | locatedInFjordSystem |
P196274
|
FINISHED |
| Object | Ofotfjorden–Rombaksfjorden system |
—
|
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: Ofotfjorden–Rombaksfjorden system | Statement: [Hålogaland Bridge, locatedInFjordSystem, Ofotfjorden–Rombaksfjorden system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInFjordSystem Context triple: [Hålogaland Bridge, locatedInFjordSystem, Ofotfjorden–Rombaksfjorden system]
-
A.
hasFjord
Indicates that an entity possesses, contains, or is characterized by a fjord as part of its geography or features.
-
B.
hasNearbyFjord
Indicates that one entity is located close to or in the vicinity of a fjord associated with another entity.
-
C.
locatedInGeographicFeature
Indicates that something is situated within or on a specific natural geographic feature (such as a mountain, river, valley, or lake).
-
D.
isInFylke
Indicates that one entity (typically a place or municipality) is located within a specific Norwegian county (fylke).
-
E.
locatedInBayOf
Indicates that something is situated within or directly on a specific bay.
- F. None of above. chosen
Provenance (4 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_69eee9b9d7708190a15d7485709ae981 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69fe1fd637c08190aa95cd2478c278cb |
completed | May 8, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69fe19344bb481909b5e2144155e4add |
completed | May 8, 2026, 5:11 p.m. |
| PDg | Predicate description generation | batch_69fe1fd58ad8819093d3d705e8521014 |
completed | May 8, 2026, 5:39 p.m. |
Created at: April 27, 2026, 5:22 a.m.