Triple
T1030616
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Visby |
E22241
|
entity |
| Predicate | locatedOn |
P40
|
FINISHED |
| Object | Gotland |
E22241
|
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: Gotland | Statement: [Visby, locatedOn, Gotland]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gotland Context triple: [Visby, locatedOn, Gotland]
-
A.
Gotland
chosen
Gotland is Sweden’s largest island, located in the Baltic Sea and known for its medieval town of Visby, limestone cliffs, and rich Viking-era history.
-
B.
Öland
Öland is Sweden’s second-largest island, known for its unique limestone plains, rich birdlife, and popular summer tourism along the Baltic Sea coast.
-
C.
Bornholm
Bornholm is a Danish island known for its rocky coastline, medieval ruins, and picturesque fishing villages in the Baltic Sea.
-
D.
Lidingö
Lidingö is a suburban island town in the Stockholm archipelago known for its affluent residential areas, natural landscapes, and proximity to Sweden’s capital.
-
E.
Rügen
Rügen is Germany’s largest island, known for its chalk cliffs, seaside resorts, and beaches along the Baltic Sea coast.
- 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_69a493d848848190aed4011b34b2e8d3 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b810429081908a97014ca740824b |
completed | March 1, 2026, 10:05 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ac429675bc8190b2467ac86c41c3b5 |
completed | March 7, 2026, 3:21 p.m. |
Created at: March 1, 2026, 7:41 p.m.