Triple

T21208175
Position Surface form Disambiguated ID Type / Status
Subject Torgu municipality E522644 entity
Predicate containsSettlement P847 FINISHED
Object Torgu-Torgu 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: Torgu-Torgu | Statement: [Torgu municipality, containsSettlement, Torgu-Torgu]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Torgu-Torgu
Context triple: [Torgu municipality, containsSettlement, Torgu-Torgu]
  • A. Torgu chosen
    Torgu is a small village in Saare County, Estonia, located on the island of Saaremaa.
  • B. Torgos
    Torgos is a genus of large Old World vultures best known for including the lappet-faced vulture.
  • C. Gorgany
    Gorgany is a rugged mountain range in the Eastern Carpathians of western Ukraine, known for its dense forests, rocky terrain, and rich biodiversity.
  • D. Turgi
    Turgi is a small Swiss municipality in the canton of Aargau, known for its residential character and proximity to the town of Baden.
  • E. Torgya
    Torgya is a traditional Buddhist festival of the Monpa people in Arunachal Pradesh, India, marked by ritual dances, masked performances, and prayers for peace and prosperity.
  • 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_69e0b5112d8881909510b2dcdc93106d completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e734362c788190bc1b96d3b84c0ad1 completed April 21, 2026, 8:24 a.m.
Created at: April 16, 2026, 3:25 p.m.