Triple

T19354178
Position Surface form Disambiguated ID Type / Status
Subject Battle of Goito E484094 entity
Predicate location P40 FINISHED
Object Goito 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: Goito | Statement: [Battle of Goito, location, Goito]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Goito
Context triple: [Battle of Goito, location, Goito]
  • A. Goito chosen
    Goito is a small historic town in the Lombardy region of northern Italy, situated along the Mincio River.
  • B. Barugo
    Barugo is a coastal municipality in the province of Leyte in the Eastern Visayas region of the Philippines, known for its agricultural economy and rural communities.
  • C. Go-Toba
    Go-Toba was a late 12th- to early 13th-century Japanese emperor known for his cultural patronage, especially of poetry, and for leading the failed Jōkyū War against the Kamakura shogunate.
  • D. Zestaponi
    Zestaponi is an industrial town in western Georgia known historically for its manganese processing and role as a regional transport hub.
  • E. Tororo
    Tororo is a town in eastern Uganda known as an important commercial and transport hub near the Kenyan border.
  • 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_69d8e8d244f8819080eb1f3491300db2 completed April 10, 2026, 12:10 p.m.
NER Named-entity recognition batch_69e6190794188190a94de464d985b5fd completed April 20, 2026, 12:16 p.m.
Created at: April 10, 2026, 1:34 p.m.