Triple

T9750491
Position Surface form Disambiguated ID Type / Status
Subject Gail Devers E236427 entity
Predicate familyName P18 FINISHED
Object Devers E234429 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: Devers | Statement: [Gail Devers, familyName, Devers]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Devers
Context triple: [Gail Devers, familyName, Devers]
  • A. Devers chosen
    Devers is a surname most notably associated with U.S. Army General Jacob L. Devers, a senior commander in the European Theater during World War II.
  • B. Fredendall
    Fredendall is the surname of Lloyd Fredendall, a U.S. Army lieutenant general noted for his controversial leadership during World War II, particularly in the North African campaign.
  • C. Bayard
    Bayard is a small town in Grant County, West Virginia, known historically as a coal and timber community in the Appalachian region.
  • D. Bayard
    Bayard is a small rural city in western Nebraska known for its agricultural community and proximity to landmarks like Chimney Rock.
  • E. Bayard
    Bayard is a masculine given name most notably associated with civil rights leader Bayard Rustin.
  • 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_69ca84d4eddc8190996fec1417d2bae8 completed March 30, 2026, 2:12 p.m.
NER Named-entity recognition batch_69cd9f6bb4088190ab8d52ef61d24bee completed April 1, 2026, 10:42 p.m.
NED1 Entity disambiguation (via context triple) batch_69d1b020829481908456e7977c5f9adb completed April 5, 2026, 12:43 a.m.
Created at: March 30, 2026, 8:24 p.m.