Triple

T5840003
Position Surface form Disambiguated ID Type / Status
Subject Coburn E129566 entity
Predicate hasNotablePersonWithGivenName P66645 FINISHED
Object Coburn H. Wood NE NERFINISHED

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: Coburn H. Wood | Statement: [Coburn, hasNotablePersonWithGivenName, Coburn H. Wood]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasNotablePersonWithGivenName
Context triple: [Coburn, hasNotablePersonWithGivenName, Coburn H. Wood]
  • A. hasNotablePersonWithSurname
    Indicates that an entity is associated with at least one notable person who bears a specified surname.
  • B. hasNotablePersonConnection
    Indicates that there exists a significant or noteworthy personal, professional, or historical relationship between the subject and the referenced person.
  • C. hasNotablePersonAsFace
    Indicates that an entity is publicly represented or symbolized by a specific notable person, such as a spokesperson, ambassador, or brand face.
  • D. notableCulturalFigure
    Indicates that a person holds significant influence or recognition within a culture’s arts, traditions, values, or public life.
  • E. notablePersonDiscussed
    Indicates that the subject entity includes or features a discussion about the referenced notable person.
  • F. None of above. chosen

Provenance (4 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_69c0084af79c81908af128ccc29983d0 completed March 22, 2026, 3:18 p.m.
NER Named-entity recognition batch_69c03c9239e08190bff7ef2bd6d21ae0 completed March 22, 2026, 7:01 p.m.
PD Predicate disambiguation batch_69c0334412388190bc594794ec5754f9 completed March 22, 2026, 6:21 p.m.
PDg Predicate description generation batch_69c03c8d579081909d7b97fc9014b5d7 completed March 22, 2026, 7:01 p.m.
Created at: March 22, 2026, 3:54 p.m.