Triple
T23937966
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pipervika |
E602693
|
entity |
| Predicate | locatedInBayOrCoastalArea |
P109263
|
FINISHED |
| Object | Oslofjord |
—
|
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: Oslofjord | Statement: [Pipervika, locatedInBayOrCoastalArea, Oslofjord]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInBayOrCoastalArea Context triple: [Pipervika, locatedInBayOrCoastalArea, Oslofjord]
-
A.
locatedOnCoastAt
Indicates that one entity is situated on the coastline at the specific location represented by another entity.
-
B.
isCoastalLocation
Indicates that a location is situated on or directly adjacent to a sea, ocean, or significant coastal body of water.
-
C.
isCoastalLocality
Indicates that a locality is situated on or directly adjacent to a sea, ocean, or significant coastal body of water.
-
D.
locatedInBayOf
chosen
Indicates that something is situated within or directly on a specific bay.
-
E.
isCoastalArea
Indicates that a given area is located along or directly adjacent to a sea or ocean coastline.
- F. None of above.
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_69e2953cf6e081909b8e25a10a52dddc |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1cfa1336c8190ac307a1b9497ba0b |
completed | April 29, 2026, 9:30 a.m. |
| PD | Predicate disambiguation | batch_69f1615518088190a206f54e2fdb14a3 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 9:06 p.m.