Triple

T20137620
Position Surface form Disambiguated ID Type / Status
Subject Harju maakond E491063 entity
Predicate contains P35 FINISHED
Object Saue 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: Saue | Statement: [Harju maakond, contains, Saue]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Saue
Context triple: [Harju maakond, contains, Saue]
  • A. Saue chosen
    Saue is a small town in northern Estonia that serves as a local administrative and residential center within the Tallinn metropolitan area.
  • B. Suau
    Suau is an Oceanic language spoken by communities in southeastern Papua New Guinea, particularly in Milne Bay Province.
  • C. Karosta
    Karosta is a historic former military port district in the Latvian city of Liepāja, known for its Tsarist-era fortifications, Soviet naval heritage, and distinctive coastal landscape.
  • D. Smedvig
    Smedvig is a Norwegian family name most prominently associated with the Smedvig shipping and oil services business dynasty.
  • E. Saane
    The Saane, also known as the Sarine, is a major river in western Switzerland that flows through the canton of Fribourg before joining the Aare.
  • 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.