Triple

T11365731
Position Surface form Disambiguated ID Type / Status
Subject J. Gresham Machen E269199 entity
Predicate familyName P18 FINISHED
Object Machen E269199 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: Machen | Statement: [J. Gresham Machen, familyName, Machen]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Machen
Context triple: [J. Gresham Machen, familyName, Machen]
  • A. Machen chosen
    Machen is a surname most notably associated with J. Gresham Machen, an influential early 20th-century American Presbyterian theologian and New Testament scholar.
  • B. Makonnen
    Makonnen is an Ethiopian nobleman and military leader best known as the father of Emperor Haile Selassie I.
  • C. Made
    Made is a town in the Dutch province of North Brabant, known as one of the population centers within the municipality of Drimmelen.
  • D. MaK
    MaK is a German engineering and manufacturing company historically known for producing heavy machinery, locomotives, and military vehicles.
  • E. Deing
    Deing is a lesser-known Papuan language spoken on the Alor–Pantar archipelago in eastern Indonesia.
  • 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_69d6aacca1048190b39dbbc2174616fa completed April 8, 2026, 7:21 p.m.
NER Named-entity recognition batch_69d7ea88558c8190aa18881af51a7b96 completed April 9, 2026, 6:06 p.m.
NED1 Entity disambiguation (via context triple) batch_69e55667d4908190b6290135eba41e54 completed April 19, 2026, 10:25 p.m.
Created at: April 8, 2026, 9:33 p.m.