Triple
T26873615
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lillebælt |
E676682
|
entity |
| Predicate | hasRegionOnShore |
P4655
|
FINISHED |
| Object | Region of Southern Denmark |
—
|
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: Region of Southern Denmark | Statement: [Lillebælt, hasRegionOnShore, Region of Southern Denmark]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRegionOnShore Context triple: [Lillebælt, hasRegionOnShore, Region of Southern Denmark]
-
A.
hasCityOnShore
Indicates that a city is located on or directly adjacent to the shore of a body of water.
-
B.
hasCoastalRegion
chosen
Indicates that a place possesses at least one region that borders or is directly adjacent to a sea or ocean.
-
C.
hasShoreOn
Indicates that one geographic entity borders or is directly adjacent to the shore of another body of water.
-
D.
hasOnItsCoast
Indicates that a geographic entity (such as a country or region) borders and includes along its shoreline another entity (such as a sea, ocean, or body of water).
-
E.
hasCoastlineOn
Indicates that one entity’s coastline borders or is directly adjacent to a specified body of water.
- 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_69eee9bb44988190b6e11652d028bc59 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69fe2f078c24819082ba396b56f02808 |
completed | May 8, 2026, 6:44 p.m. |
| PD | Predicate disambiguation | batch_69fe228fe1988190baf3bb34897f3dbe |
completed | May 8, 2026, 5:51 p.m. |
Created at: April 27, 2026, 5:34 a.m.