Triple
T20137939
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Viimsi Peninsula |
E491073
|
entity |
| Predicate | containsSettlement |
P847
|
FINISHED |
| Object | Lubja |
—
|
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: Lubja | Statement: [Viimsi Peninsula, containsSettlement, Lubja]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lubja Context triple: [Viimsi Peninsula, containsSettlement, Lubja]
-
A.
Lubja
chosen
Lubja is a small village located within Viimsi Parish in northern Estonia, near the capital city of Tallinn.
-
B.
Lujza
Lujza is a given name, primarily used in Central and Eastern Europe, that corresponds to the name Luisa or Louise in other languages.
-
C.
Ludza
Ludza is one of the principal towns of the Latgale region in eastern Latvia, known for its historic castle ruins and status as one of the country’s oldest settlements.
-
D.
Libo
Libo is an ancient Roman cognomen associated with members of the patrician Julii family.
-
E.
Liuboml
Liuboml is a small historic town in western Ukraine near the Polish border, known for its medieval roots and multicultural heritage.
- 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.