Triple

T777205
Position Surface form Disambiguated ID Type / Status
Subject Imereti E16413 entity
Predicate hasCity P316 FINISHED
Object Kutaisi E7705 NE FINISHED

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: Kutaisi | Statement: [Imereti, hasCity, Kutaisi]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kutaisi
Context triple: [Imereti, hasCity, Kutaisi]
  • A. Kutaisi chosen
    Kutaisi is one of Georgia’s major cities, historically significant and formerly a capital, located in the western part of the country.
  • B. Kut
    Kut is a city in eastern Iraq situated on the banks of the Tigris River, known historically as a strategic location and the site of significant World War I battles.
  • C. Kohat
    Kohat is a historic city in northwestern Pakistan known for its strategic location, military cantonment, and role as a regional administrative and commercial center.
  • D. Senja
    Senja is Norway’s second-largest island, renowned for its dramatic coastal mountains, fishing villages, and scenic Arctic landscapes.
  • E. Vianen
    Vianen is a historic Dutch town known for its medieval city center and location near major rivers in the western Netherlands.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (3 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_69a4936ad1fc81908f190208059ccf78 completed March 1, 2026, 7:28 p.m.
NER Named-entity recognition batch_69a4a74da7648190adfad56717d564df completed March 1, 2026, 8:53 p.m.
NED1 Entity disambiguation (via context triple) batch_69a7b83be4f88190ab5f969f4f52924e completed March 4, 2026, 4:42 a.m.
Created at: March 1, 2026, 7:37 p.m.