Triple

T18940350
Position Surface form Disambiguated ID Type / Status
Subject Joseph Bové E463363 entity
Predicate familyName P18 FINISHED
Object Bové 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: Bové | Statement: [Joseph Bové, familyName, Bové]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bové
Context triple: [Joseph Bové, familyName, Bové]
  • A. Bové chosen
    Bové is the surname of Joseph Bové, a prominent 19th-century architect known for helping shape the neoclassical appearance of central Moscow.
  • B. Kurów
    Kurów is a village in eastern Poland best known as the birthplace of former Polish leader Wojciech Jaruzelski.
  • C. Ushi
    Ushi is the affectionate nickname of Japanese professional football club Vissel Kobe, reflecting its local identity and fan culture.
  • D. Bovianum
    Bovianum was an important ancient city that served as a principal center of the Samnite people in south-central Italy.
  • E. Vitulano
    Vitulano is a small Italian town and municipality nestled in the mountainous area of the Campania region’s Benevento province, known for its rural character and scenic surroundings.
  • 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_69d8dcfec90481909e926be9767e5779 completed April 10, 2026, 11:20 a.m.
NER Named-entity recognition batch_69e5d3eae9b88190b6031c359090782a completed April 20, 2026, 7:21 a.m.
Created at: April 10, 2026, 11:59 a.m.