Triple

T1230993
Position Surface form Disambiguated ID Type / Status
Subject Gregory Hines E26441 entity
Predicate familyName P18 FINISHED
Object Hines E120757 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: Hines | Statement: [Gregory Hines, familyName, Hines]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hines
Context triple: [Gregory Hines, familyName, Hines]
  • A. Hines chosen
    Hines is a surname most famously associated with Earl Hines, the influential American jazz pianist and bandleader.
  • B. Hayes
    Hayes is a suburban district in southeast London, England, known for its residential character and green spaces within the London Borough of Bromley.
  • C. Harbison
    Harbison is a surname most notably associated with American composer John Harbison, known for his contributions to contemporary classical music.
  • D. Willis
    Willis is a masculine given name and surname of English origin, often considered a variant or cognate of the name Wilson.
  • E. Harrison
    Harrison is a city in New Jersey’s Hudson County, known as a residential and industrial community within the New York metropolitan area.
  • 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_69a4948571c88190a9191e451e6035fd completed March 1, 2026, 7:33 p.m.
NER Named-entity recognition batch_69a4be585674819099218b19ca9e7c66 completed March 1, 2026, 10:31 p.m.
NED1 Entity disambiguation (via context triple) batch_69ac8a1457a08190aef2f7fed6c6725f completed March 7, 2026, 8:27 p.m.
Created at: March 1, 2026, 7:47 p.m.