Triple

T15449696
Position Surface form Disambiguated ID Type / Status
Subject Battle of Custoza (1848) E370116 entity
Predicate location P40 FINISHED
Object Custoza E503043 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: Custoza | Statement: [Battle of Custoza (1848), location, Custoza]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Custoza
Context triple: [Battle of Custoza (1848), location, Custoza]
  • A. Custoza chosen
    Custoza is an Italian white wine appellation in the Veneto region, known for producing fresh, aromatic blends from local grape varieties.
  • B. Isonzo
    The Isonzo is a river in the Julian Alps of northeastern Italy and western Slovenia, historically known as a major World War I battlefield.
  • C. Fossalta di Piave
    Fossalta di Piave is a small Italian town in the Veneto region, known for its location near the Piave River and its World War I historical significance.
  • D. Vittorio Veneto
    Vittorio Veneto is a town in northeastern Italy best known as the site of a decisive World War I battle that led to the collapse of the Austro-Hungarian front.
  • E. Gradisca d’Isonzo
    Gradisca d’Isonzo is a historic town in northeastern Italy, near the Isonzo River, known for its former role as a fortified center under Habsburg rule.
  • 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_69d85a19180081909925012fbf4e62a3 completed April 10, 2026, 2:02 a.m.
NER Named-entity recognition batch_69e03ef9334c81908541e231b43eb012 completed April 16, 2026, 1:44 a.m.
NED1 Entity disambiguation (via context triple) batch_69ff21b1e9688190a283dbc552072ce0 completed May 9, 2026, 11:59 a.m.
Created at: April 10, 2026, 3:21 a.m.