Triple

T19396976
Position Surface form Disambiguated ID Type / Status
Subject Frank S. Nugent E485216 entity
Predicate familyName P18 FINISHED
Object Nugent 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: Nugent | Statement: [Frank S. Nugent, familyName, Nugent]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Nugent
Context triple: [Frank S. Nugent, familyName, Nugent]
  • A. Nugent chosen
    Nugent is a surname of Irish origin historically associated with Anglo-Norman nobility and borne by various notable figures in politics, the arts, and public life.
  • B. Nouster
    Nouster is a small settlement on the Orkney island of North Ronaldsay in Scotland.
  • C. Ebersole
    Ebersole is a surname most notably associated with American actress and singer Christine Ebersole.
  • D. Tilghman
    Tilghman is a masculine given name of English origin that has been borne by various notable American figures, including politicians and military officers.
  • E. Tilghman
    Tilghman is a surname most notably associated with Shirley M. Tilghman, a prominent molecular biologist and former president of Princeton University.
  • 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_69d8e8d5162481909db12435d9535c1a completed April 10, 2026, 12:11 p.m.
NER Named-entity recognition batch_69e62573f5788190a635b92121db2cf7 completed April 20, 2026, 1:09 p.m.
Created at: April 10, 2026, 1:36 p.m.