Triple
T32890169
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roskilde Fjord |
E841308
|
entity |
| Predicate | passesMunicipality |
P10456
|
FINISHED |
| Object | Roskilde Municipality |
—
|
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: Roskilde Municipality | Statement: [Roskilde Fjord, passesMunicipality, Roskilde Municipality]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: passesMunicipality Context triple: [Roskilde Fjord, passesMunicipality, Roskilde Municipality]
-
A.
passesCity
chosen
Indicates that a route, path, or journey goes through or traverses a particular city as part of its course.
-
B.
isInMunicipality
Indicates that one entity (typically a place or address) is located within the administrative boundaries of a specific municipality.
-
C.
isMunicipalHomeOf
Indicates that a municipality serves as the official home base or hosting location for a particular entity or organization.
-
D.
spansMunicipality
Indicates that something (such as an area, structure, or feature) extends across or covers more than one municipality.
-
E.
isPortMunicipality
Indicates that a municipality functions as a port, having facilities for maritime transport and related activities.
- 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_69f74062b9388190b30546cf700a825c |
completed | May 3, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69f73c802b848190b61a416b7488bd96 |
completed | May 3, 2026, 12:16 p.m. |
Created at: May 1, 2026, 1:18 a.m.