Triple

T17839567
Position Surface form Disambiguated ID Type / Status
Subject Ivanava District E445486 entity
Predicate hasSettlement P1068 FINISHED
Object Ivanava 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: Ivanava | Statement: [Ivanava District, hasSettlement, Ivanava]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ivanava
Context triple: [Ivanava District, hasSettlement, Ivanava]
  • A. Ivanava chosen
    Ivanava is a town in southwestern Belarus that serves as a local administrative and cultural center.
  • B. Nakoruru
    Nakoruru is a popular Samurai Shodown character known as a nature-loving Ainu shrine maiden who fights alongside her hawk and wolf companions.
  • C. Ivisan
    Ivisan is a coastal municipality in the province of Capiz in the Western Visayas region of the Philippines.
  • D. Eiryaku
    Eiryaku was a Japanese era name (nengō) of the late Heian period, used during the reign of Emperor Go-Shirakawa.
  • E. Tohana
    Tohana is a town and municipal council in the Fatehabad district of the Indian state of Haryana, known as an agricultural and trading center in the region.
  • 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_69d8b9f1a6d881909f024bc603111cdb completed April 10, 2026, 8:50 a.m.
NER Named-entity recognition batch_69e48d2a570c81909787296bde7e795c completed April 19, 2026, 8:07 a.m.
Created at: April 10, 2026, 10:16 a.m.