Triple
T6308598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heltermaa port |
E141440
|
entity |
| Predicate | serves |
P98
|
FINISHED |
| Object | Heltermaa |
E141440
|
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: Heltermaa | Statement: [Heltermaa port, serves, Heltermaa]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Heltermaa Context triple: [Heltermaa port, serves, Heltermaa]
-
A.
Heltermaa
chosen
Heltermaa is a small port village on the eastern coast of Hiiumaa Island in Estonia, serving as a key ferry connection to the mainland.
-
B.
Tutermaa
Tutermaa is a small village located in Harku Parish in northern Estonia.
-
C.
Hailuoto
Hailuoto is a Finnish island in the northern Baltic Sea known for its unique dune landscapes, birdlife, and traditional fishing villages.
-
D.
Rannamõisa
Rannamõisa is a village in northern Estonia known for its coastal location on the Baltic Sea and proximity to the capital, Tallinn.
-
E.
Ahti
Ahti is a Finnish masculine given name, historically associated with figures in Finnish mythology and borne by various notable Finns.
- 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_69c008d00efc8190a36c05b4b4a3bf4b |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0647d38008190abaf96632712ddf9 |
completed | March 22, 2026, 9:51 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c5e45330ec8190945682962ae823b0 |
completed | March 27, 2026, 1:58 a.m. |
Created at: March 22, 2026, 4:28 p.m.