Triple

T9844955
Position Surface form Disambiguated ID Type / Status
Subject Denis Noble E239317 entity
Predicate familyName P18 FINISHED
Object Noble E521381 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: Noble | Statement: [Denis Noble, familyName, Noble]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Noble
Context triple: [Denis Noble, familyName, Noble]
  • A. Noble chosen
    Noble is a surname of English origin historically associated with social rank and often borne by families of distinction.
  • B. Noble
    Noble is an unincorporated community and residential area within Abington Township in Montgomery County, Pennsylvania.
  • C. Regal
    Regal is a major American movie theater chain known for operating multiplex cinemas across the United States.
  • D. Worthy
    Worthy is the surname of James Worthy, the Hall of Fame former Los Angeles Lakers basketball star known for his clutch playoff performances in the 1980s.
  • E. Lofty
    Lofty is the nickname of Nat Lofthouse, the legendary English footballer famed for his prolific goal-scoring with Bolton Wanderers and England in the mid-20th century.
  • 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_69ca84e3f0c48190ada72a65ebd50efd completed March 30, 2026, 2:12 p.m.
NER Named-entity recognition batch_69cdb35ff7848190a8a717773d8654b9 completed April 2, 2026, 12:08 a.m.
NED1 Entity disambiguation (via context triple) batch_69d1d5dda4b0819092703270e87bee5a completed April 5, 2026, 3:24 a.m.
Created at: March 30, 2026, 8:33 p.m.