Triple

T8144148
Position Surface form Disambiguated ID Type / Status
Subject Honora Burke E190166 entity
Predicate givenName P17 FINISHED
Object Honora E243280 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: Honora | Statement: [Honora Burke, givenName, Honora]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Honora
Context triple: [Honora Burke, givenName, Honora]
  • A. Honora chosen
    Honora is a feminine given name of Latin origin meaning "honor" or "woman of honor."
  • B. Cornelia
    Cornelia is a feminine given name of Latin origin, historically associated with several notable women in European history.
  • C. Horatia
    Horatia is a feminine given name most notably borne by Horatia Nelson, the daughter of British naval hero Admiral Horatio Nelson and Emma Hamilton.
  • D. Constance
    Constance is a feminine given name of Latin origin, historically associated with nobility and meaning steadfastness or constancy.
  • E. Constance
    Constance is a historic city on Lake Constance in present-day Germany, best known as the site of the early 15th-century Council of Constance that ended the Western Schism in the Catholic Church.
  • 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_69ca82bd9900819099477cdc2eb4244f completed March 30, 2026, 2:03 p.m.
NER Named-entity recognition batch_69cb4444bb248190beaaa2ce4b8f3eaa completed March 31, 2026, 3:49 a.m.
NED1 Entity disambiguation (via context triple) batch_69cc94b0fc0481909a21f42364a92158 completed April 1, 2026, 3:44 a.m.
Created at: March 30, 2026, 5:36 p.m.