Triple
T22714034
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orissaare |
E561677
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Saaremaa |
—
|
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: Saaremaa | Statement: [Orissaare, locatedIn, Saaremaa]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Saaremaa Context triple: [Orissaare, locatedIn, Saaremaa]
-
A.
Saaremaa
chosen
Saaremaa is the largest island of Estonia, known for its rugged coastline, medieval Kuressaare Castle, and distinctive windmills and juniper landscapes.
-
B.
Naissaar
Naissaar is a forested Estonian island in the Baltic Sea known for its military history, nature reserves, and proximity to Tallinn.
-
C.
Hiiumaa
Hiiumaa is Estonia’s second-largest island, located in the Baltic Sea and known for its unspoiled nature, lighthouses, and quiet rural landscapes.
-
D.
Märjamaa
Märjamaa is a small borough in western Estonia that serves as a local administrative and service center within Rapla County.
-
E.
Kuressaare
Kuressaare is the main town on Estonia’s Saaremaa island, known for its well-preserved medieval castle and seaside spa resort atmosphere.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e2454f1348819088d83f420925a5c1 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1790bdac88190976c83c9039c9d16 |
completed | April 29, 2026, 3:20 a.m. |
Created at: April 17, 2026, 3:18 p.m.