Triple

T15466711
Position Surface form Disambiguated ID Type / Status
Subject will-helmet E372047 entity
Predicate isRelatedToName P3889 FINISHED
Object William E772 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: William | Statement: [will-helmet, isRelatedToName, William]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: William
Context triple: [will-helmet, isRelatedToName, William]
  • A. William chosen
    William is a common masculine given name of Germanic origin, widely used in English-speaking countries.
  • B. Thomas
    Thomas is the given name of Thomas Fairfax, 1st Lord Fairfax of Cameron, a prominent Parliamentarian general during the English Civil War.
  • C. Thomas
    Thomas is the given name of Thomas Fairfax, 2nd Lord Fairfax of Cameron, a prominent Parliamentary general during the English Civil War.
  • D. Thomas
    Thomas is the given first name of American actor Tom Sizemore, known for his intense supporting roles in crime and war films.
  • E. Thomas
    Thomas is the formal given name of the American author and journalist Tom Wolfe, known for his pioneering work in New Journalism.
  • 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_69d85cc8bd308190886949510b42e764 completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69e03f69a31c81909a749247b6615d91 completed April 16, 2026, 1:46 a.m.
NED1 Entity disambiguation (via context triple) batch_69ff2d01a23c819095cf75b7d5a801a9 completed May 9, 2026, 12:48 p.m.
Created at: April 10, 2026, 3:33 a.m.