Triple
T20137940
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Viimsi Peninsula |
E491073
|
entity |
| Predicate | containsSettlement |
P847
|
FINISHED |
| Object | Tammneeme |
—
|
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: Tammneeme | Statement: [Viimsi Peninsula, containsSettlement, Tammneeme]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Tammneeme Context triple: [Viimsi Peninsula, containsSettlement, Tammneeme]
-
A.
Tammneeme
chosen
Tammneeme is a coastal village in northern Estonia known for its seaside location on the Viimsi Peninsula near Tallinn.
-
B.
Leppneeme
Leppneeme is a coastal village in northern Estonia known for its small harbor and proximity to the capital, Tallinn.
-
C.
Nõmme
Nõmme is a leafy, villa-filled suburban district of Tallinn known for its pine forests, wooden architecture, and small-town atmosphere within the capital.
-
D.
Õismäe
Õismäe is a residential subdistrict of Tallinn, Estonia, known for its large Soviet-era apartment blocks and distinctive circular street layout.
-
E.
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.
- 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_69da62651a0c8190a3e05e95e056a66b |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e6676879f48190a59da04393d2a8cc |
completed | April 20, 2026, 5:50 p.m. |
Created at: April 11, 2026, 11:32 p.m.