Triple
T14754276
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baltic Sea trade routes |
E346688
|
entity |
| Predicate | hasImportantPort |
P6498
|
FINISHED |
| Object | Visby |
E152807
|
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: Visby | Statement: [Baltic Sea trade routes, hasImportantPort, Visby]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Visby Context triple: [Baltic Sea trade routes, hasImportantPort, Visby]
-
A.
Visby
chosen
Visby is a well-preserved medieval Hanseatic town on the Swedish island of Gotland, renowned for its historic city wall and UNESCO World Heritage status.
-
B.
Karlskrona
Karlskrona is a historic Swedish coastal city and naval base known for its well-preserved maritime architecture and UNESCO-listed naval port.
-
C.
Halmstad
Halmstad is a coastal city in southwestern Sweden known for its historic town center, harbor, and role as a strategic site in Scandinavian conflicts.
-
D.
Halmstad
Halmstad is a village in Moss municipality in Viken county, southeastern Norway.
-
E.
Kristianstad
Kristianstad is a historic city in southern Sweden known for its well-preserved Renaissance architecture and proximity to the wetlands of the Kristianstad Vattenrike Biosphere Reserve.
- 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_69d822e8896c819091169882f9b20486 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dec7d59df08190a86da5048358bd6e |
completed | April 14, 2026, 11:03 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fdfb9c725881908004368772fa528d |
completed | May 8, 2026, 3:05 p.m. |
Created at: April 10, 2026, 1:30 a.m.