Triple

T20291587
Position Surface form Disambiguated ID Type / Status
Subject Brigham E510038 entity
Predicate hasVariantForm P457 FINISHED
Object Briggam 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: Briggam | Statement: [Brigham, hasVariantForm, Briggam]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Briggam
Context triple: [Brigham, hasVariantForm, Briggam]
  • A. Brigham chosen
    Brigham is a masculine given name most notably borne by Brigham Young, the 19th-century American religious leader and second president of The Church of Jesus Christ of Latter-day Saints.
  • B. Kittredge
    Kittredge is an English-language surname borne by various notable figures, including American writer Charmian Kittredge London.
  • C. Leahey
    Leahey is a surname variant of Leahy, an Irish family name of Gaelic origin.
  • D. Talmage
    Talmage is a given name and surname of English origin that appears as the middle name of American socialite Madeleine Talmage Force.
  • E. Fairley
    Fairley is a surname and given name, often considered a variant spelling of Farley, that appears in English-speaking countries.
  • 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_69e0b4c652388190b782cad965e5a098 completed April 16, 2026, 10:07 a.m.
NER Named-entity recognition batch_69e67700c024819091205f5b0a8648e3 completed April 20, 2026, 6:57 p.m.
Created at: April 16, 2026, 11:12 a.m.