Triple

T20463806
Position Surface form Disambiguated ID Type / Status
Subject Glehn Castle E501995 entity
Predicate locatedNear P294 FINISHED
Object Nõmme centre 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: Nõmme centre | Statement: [Glehn Castle, locatedNear, Nõmme centre]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Nõmme centre
Context triple: [Glehn Castle, locatedNear, Nõmme centre]
  • A. 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.
  • B. Nõmme Adventure Park
    Nõmme Adventure Park is an outdoor recreation area in Tallinn, Estonia, featuring treetop obstacle courses, zip lines, and other adventure activities set in a forest environment.
  • C. Nõmme district chosen
    Nõmme district is a largely residential, green and hilly district of Tallinn, Estonia, known for its pine forests, wooden houses and villa-style architecture.
  • D. Nõmmküla
    Nõmmküla is a small village located on Muhu Island in Estonia.
  • E. Pärnamäe
    Pärnamäe is a village located in Viimsi Parish in northern Estonia, near the capital city 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_69e0b4ad4940819098cf2ff6413574e5 completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e696a88374819087e7b97c83074d2c completed April 20, 2026, 9:12 p.m.
Created at: April 16, 2026, 11:33 a.m.