Triple
T8405940
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Belt |
E198498
|
entity |
| Predicate | separates |
P1175
|
FINISHED |
| Object | Zealand |
E38167
|
NE 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: Zealand | Statement: [Great Belt, separates, Zealand]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Zealand Context triple: [Great Belt, separates, Zealand]
-
A.
Zealand
chosen
Zealand is the largest and most populous island of Denmark, home to the capital city Copenhagen and a central hub of the country’s cultural and economic life.
-
B.
Vestland
Vestland is a county in western Norway known for its dramatic fjords, coastal landscapes, and the city of Bergen.
-
C.
Schwedeninsel
Schwedeninsel is a small, wooded island located in the Bavarian lake Ammersee in southern Germany.
-
D.
Åboland
Åboland is a Swedish-speaking coastal and archipelago region in southwestern Finland known for its strong cultural and linguistic ties to the Swedish minority.
-
E.
Mykland
Mykland is a small village in Agder county, Norway, known for its rural setting and surrounding forests and lakes.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69ca8310df9c8190b25f16161cca3e41 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cb8312941c8190af0b2def0a4e02be |
completed | March 31, 2026, 8:17 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ce03035e148190867b60ddaeb8d761 |
completed | April 2, 2026, 5:47 a.m. |
Created at: March 30, 2026, 6:05 p.m.