Triple
T32890368
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kronprins Frederiks Bro |
E841314
|
entity |
| Predicate | fjordSection |
P56784
|
FINISHED |
| Object | Inner Roskilde Fjord |
—
|
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: Inner Roskilde Fjord | Statement: [Kronprins Frederiks Bro, fjordSection, Inner Roskilde Fjord]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fjordSection Context triple: [Kronprins Frederiks Bro, fjordSection, Inner Roskilde Fjord]
-
A.
hasFjord
chosen
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.
bodyOfWaterCrossedByFerry
Indicates that a body of water is traversed or crossed by a ferry service.
-
D.
JøssingfjordRole
Indicates that an entity plays a specific role or has a particular involvement in relation to the historical events or context associated with Jøssingfjord.
-
E.
watercourseSectionOf
Indicates that a watercourse segment forms a constituent part of a larger watercourse.
- 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_69f34945ae408190b72d8118c83beb77 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d16f5cb881908eed141afaaa0b51 |
completed | May 3, 2026, 4:39 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe45554819089cbbd538d992132 |
completed | May 3, 2026, 4:32 a.m. |
Created at: May 1, 2026, 1:18 a.m.