Triple
T19816812
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Viimsi |
E476078
|
entity |
| Predicate | hasAdministrativeCentre |
P1474
|
FINISHED |
| Object | Haabneeme |
—
|
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: Haabneeme | Statement: [Viimsi, hasAdministrativeCentre, Haabneeme]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Haabneeme Context triple: [Viimsi, hasAdministrativeCentre, Haabneeme]
-
A.
Haabneeme
chosen
Haabneeme is a small coastal settlement in northern Estonia, located on the Viimsi Peninsula near Tallinn.
-
B.
Herbaijum
Herbaijum is a small village in the province of Friesland in the Netherlands.
-
C.
Mahmee
Mahmee is a maternal and infant healthcare startup that provides technology-enabled care coordination and support for new and expecting parents.
-
D.
Hamul
Hamul is a minor biblical figure listed in the Book of Genesis as one of the descendants of Judah and a member of the early Israelite family lineage.
-
E.
Hannut
Hannut is a municipality in the French-speaking Walloon Region of Belgium, known for its rural character and location between Liège and Brussels.
- 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_69d8e51bc4208190a1c57d8c5d1b15e4 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e654f9c5b08190987237f5144c3b37 |
completed | April 20, 2026, 4:31 p.m. |
Created at: April 10, 2026, 1:50 p.m.