Triple

T20463741
Position Surface form Disambiguated ID Type / Status
Subject Nõmme Railway Station E501994 entity
Predicate servesSettlement P2741 FINISHED
Object Nõmme 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 | Statement: [Nõmme Railway Station, servesSettlement, Nõmme]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Nõmme
Context triple: [Nõmme Railway Station, servesSettlement, Nõmme]
  • A. Nõmme chosen
    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. Nurmes
    Nurmes is a small town and municipality in eastern Finland known for its lakeside scenery and traditional Karelian culture.
  • C. Tammneeme
    Tammneeme is a coastal village in northern Estonia known for its seaside location on the Viimsi Peninsula near Tallinn.
  • D. Nõmmküla
    Nõmmküla is a small village located on Muhu Island in Estonia.
  • E. Kuusalu
    Kuusalu is a small borough in northern Estonia that serves as the main local hub for administration, services, and community life in the surrounding rural area.
  • 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.