Triple

T19381686
Position Surface form Disambiguated ID Type / Status
Subject Vanna Venturi E484824 entity
Predicate familyName P18 FINISHED
Object Venturi 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: Venturi | Statement: [Vanna Venturi, familyName, Venturi]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Venturi
Context triple: [Vanna Venturi, familyName, Venturi]
  • A. Venturi chosen
    Venturi is an Italian surname most prominently associated with architect Robert Venturi, a key figure in postmodern architecture.
  • B. Vane
    Vane is an English surname historically associated with several notable aristocratic and political families in Britain.
  • C. Vitesse
    Vitesse is a professional Dutch football club based in Arnhem that competes in the country's top leagues and European competitions.
  • D. Venucia
    Venucia is a Chinese automobile marque known for producing affordable passenger vehicles, originally established as a local brand under the Renault–Nissan–Mitsubishi Alliance.
  • E. Viskan
    Viskan is a river in southwestern Sweden that flows through the province of Halland into the Kattegat.
  • 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_69d8e8d460d88190abf0591c5c9d2b0c completed April 10, 2026, 12:11 p.m.
NER Named-entity recognition batch_69e61a6075a88190aed7afa3b8fd3021 completed April 20, 2026, 12:21 p.m.
Created at: April 10, 2026, 1:35 p.m.