Triple

T2489576
Position Surface form Disambiguated ID Type / Status
Subject Philip Vian E52006 entity
Predicate familyName P18 FINISHED
Object Vian E63875 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: Vian | Statement: [Philip Vian, familyName, Vian]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Vian
Context triple: [Philip Vian, familyName, Vian]
  • A. Vian chosen
    Vian is a surname most notably associated with British Royal Navy Admiral Philip Vian, who served with distinction during both World Wars.
  • B. Verny
    Verny was the historical name of the city now known as Almaty, a major cultural and economic center in Kazakhstan.
  • C. Corine
    Corine is a feminine given name used in various European countries, often considered a variant of "Corinne."
  • D. Valleiry
    Valleiry is a small French commune in the Haute-Savoie department of the Auvergne-Rhône-Alpes region in southeastern France, near the Swiss border.
  • E. Vichy
    Vichy is a spa town in central France renowned for its thermal springs, health resorts, and role as the seat of the World War II Vichy regime.
  • 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_69ab4955111c8190835bf619adec21ff completed March 6, 2026, 9:38 p.m.
NER Named-entity recognition batch_69abd17b7a048190bcc8f0a66514a052 completed March 7, 2026, 7:19 a.m.
NED1 Entity disambiguation (via context triple) batch_69af1f8ee974819082a2a29f8b72d131 completed March 9, 2026, 7:29 p.m.
Created at: March 6, 2026, 9:45 p.m.