Triple

T23150026
Position Surface form Disambiguated ID Type / Status
Subject John Mercer Langston E578297 entity
Predicate middleName P143 FINISHED
Object Mercer 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: Mercer | Statement: [John Mercer Langston, middleName, Mercer]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Mercer
Context triple: [John Mercer Langston, middleName, Mercer]
  • A. Mercer
    Mercer is a global consulting firm specializing in human resources, health, retirement, and investment solutions.
  • B. Mercer chosen
    Mercer is a surname of Scottish and English origin borne by various notable individuals, including the American Revolutionary War general Hugh Mercer.
  • C. Wilmore
    Wilmore is an English-language surname borne by various notable individuals across fields such as entertainment, sports, and public service.
  • D. Wilmore
    Wilmore is a small city in central Kentucky known for its strong Christian academic community and as the home of Asbury University and Asbury Theological Seminary.
  • E. Aiken
    Aiken is a variant spelling of the surname Aitken, which is of Scottish origin.
  • 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_69e245fb8de081908f0eba7b5fd75bc4 completed April 17, 2026, 2:38 p.m.
NER Named-entity recognition batch_69f18ed0b76c8190ac61b949d88e9970 completed April 29, 2026, 4:53 a.m.
Created at: April 17, 2026, 4:01 p.m.