Triple

T6872949
Position Surface form Disambiguated ID Type / Status
Subject Triveneto E158596 entity
Predicate contains P35 FINISHED
Object Piave River E136506 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: Piave River | Statement: [Triveneto, contains, Piave River]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Piave River
Context triple: [Triveneto, contains, Piave River]
  • A. Piave River chosen
    The Piave River is a waterway in northeastern Italy that became historically significant as the site of major battles on the Italian Front during World War I.
  • B. Adige
    The Adige is one of Italy’s longest rivers, flowing from the Alpine region of South Tyrol through cities like Bolzano and Verona before emptying into the Adriatic Sea.
  • C. Isonzo River
    The Isonzo River is a watercourse in northeastern Italy and western Slovenia, historically known as a major World War I battlefield along the Italian Front.
  • D. Brenta River
    The Brenta River is a major watercourse in northeastern Italy that flows from the Alps through the Veneto region before emptying into the Adriatic Sea.
  • E. Soligo River
    The Soligo River is a watercourse in northeastern Italy that flows through the Veneto region before joining the Piave River.
  • 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_69c68832af1481908ce356e133ebaebe completed March 27, 2026, 1:37 p.m.
NER Named-entity recognition batch_69c6d8c73ea08190b6bb1463e7ead47b completed March 27, 2026, 7:21 p.m.
NED1 Entity disambiguation (via context triple) batch_69c742af0df88190bb23b7495c279e08 completed March 28, 2026, 2:53 a.m.
Created at: March 27, 2026, 2:22 p.m.