Triple
T7488764
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Limfjord |
E176948
|
entity |
| Predicate | nowOpensTo |
P71126
|
FINISHED |
| Object | both North Sea and Kattegat |
—
|
LITERAL FINISHED |
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: both North Sea and Kattegat | Statement: [Limfjord, nowOpensTo, both North Sea and Kattegat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nowOpensTo Context triple: [Limfjord, nowOpensTo, both North Sea and Kattegat]
-
A.
openingTo
chosen
Indicates that one entity serves as an entrance, access point, or passage leading into or toward another entity.
-
B.
openingTime
Indicates the time at which a place, service, or event begins operating or becomes accessible.
-
C.
alsoOpenOn
Indicates that a place, service, or resource is open or available during an additional specified time or on an additional specified day beyond its primary opening period.
-
D.
hasOpening
Indicates that one entity possesses or features an opening, gap, or entrance that allows access, passage, or exposure.
-
E.
initiallyOpenTo
Indicates that something starts out in an open state or condition at the beginning of a process, period, or interaction.
- 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_69c69f24ac508190bb98fe927c0bd065 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f55abcd481909e42ca857fe46cd1 |
completed | March 27, 2026, 9:23 p.m. |
| PD | Predicate disambiguation | batch_69c6f03eeaa88190a5215772ed05ee9f |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:43 p.m.