Triple
T5995967
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Suuremõisa Manor Park |
E133468
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Suuremõisa |
E133468
|
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: Suuremõisa | Statement: [Suuremõisa Manor Park, locatedIn, Suuremõisa]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Suuremõisa Context triple: [Suuremõisa Manor Park, locatedIn, Suuremõisa]
-
A.
Suuremõisa
chosen
Suuremõisa is a village on the Estonian island of Hiiumaa, known for its historic manor complex and surrounding park.
-
B.
Mustamäe
Mustamäe is a residential district in the western part of Tallinn, Estonia, known for its Soviet-era apartment blocks and proximity to universities and technology hubs.
-
C.
Kivimäe
Kivimäe is a residential subdistrict within the Nõmme district of Tallinn, Estonia, known for its green, suburban character.
-
D.
Vana-Mustamäe
Vana-Mustamäe is a residential subdistrict of the Nõmme district in Tallinn, Estonia, known for its green areas and quiet, suburban character.
-
E.
Pääsküla
Pääsküla is a subdistrict of the Nõmme district in Tallinn, Estonia, known for its residential areas and nearby natural landscapes.
- 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_69c00870ddbc81909880fa3864f4f38d |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c04e963f3c819082dd755e328ab947 |
completed | March 22, 2026, 8:18 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c1136125808190a363a00a60d8675a |
completed | March 23, 2026, 10:18 a.m. |
Created at: March 22, 2026, 4:05 p.m.