Triple

T14467312
Position Surface form Disambiguated ID Type / Status
Subject Honorée E358746 entity
Predicate relatedName P3889 FINISHED
Object Honorine E361609 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: Honorine | Statement: [Honorée, relatedName, Honorine]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Honorine
Context triple: [Honorée, relatedName, Honorine]
  • A. Honorine chosen
    Honorine is a feminine given name of French origin, used both as a standalone first name and as part of compound names.
  • B. Honorée
    Honorée is the French feminine given name corresponding to Honoré, traditionally meaning "honored" or "esteemed."
  • C. Bénédicte
    Bénédicte is the given name of Louise Bénédicte de Bourbon, a French noblewoman of the House of Bourbon.
  • D. Geneviève
    Geneviève is a character in Claude Debussy’s opera "Pelléas et Mélisande," typically portrayed as the mother of Pelléas and Golaud and a figure of quiet, dignified authority within the story.
  • E. Armande
    Armande is a French given name historically associated with figures in the performing arts, notably in 17th-century France.
  • 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_69d827966698819082e140837737501d completed April 9, 2026, 10:26 p.m.
NER Named-entity recognition batch_69de91f8613c819080424104c0b7f4c3 completed April 14, 2026, 7:14 p.m.
NED1 Entity disambiguation (via context triple) batch_69fd6499c7188190a79411b471cfa7d4 completed May 8, 2026, 4:20 a.m.
Created at: April 10, 2026, 1:19 a.m.