Triple

T3691575
Position Surface form Disambiguated ID Type / Status
Subject Hank Steinbrenner E78354 entity
Predicate givenName P17 FINISHED
Object Henry E188877 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: Henry | Statement: [Hank Steinbrenner, givenName, Henry]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Henry
Context triple: [Hank Steinbrenner, givenName, Henry]
  • A. Henry
    Henry is a masculine given name of Germanic origin that has been widely used by European royalty and notable historical figures.
  • B. Henry
    Henry is the given name of Henry A. Kissinger, the influential American diplomat and political scientist who served as U.S. Secretary of State and National Security Advisor.
  • C. Henry
    Henry is the given name of the influential American architect Henry Hobson Richardson, a key figure in 19th-century architecture.
  • D. Henry
    Henry is a common English surname borne by numerous notable individuals across politics, sports, and the arts.
  • E. Henry chosen
    Henry is the given first name of Hank Steinbrenner, a late co-owner and general partner of the New York Yankees baseball team.
  • 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_69ad85e285a081908f8cbfa9e2ed9b75 completed March 8, 2026, 2:21 p.m.
NER Named-entity recognition batch_69adc4e783a88190b2837a68b8723a25 completed March 8, 2026, 6:50 p.m.
NED1 Entity disambiguation (via context triple) batch_69b4c39796648190a83a7f1a63c653bd completed March 14, 2026, 2:10 a.m.
Created at: March 8, 2026, 3:26 p.m.