Triple

T21510778
Position Surface form Disambiguated ID Type / Status
Subject Blanche Hudson E530711 entity
Predicate relationshipToFame P100676 FINISHED
Object former Hollywood celebrity LITERAL 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: former Hollywood celebrity | Statement: [Blanche Hudson, relationshipToFame, former Hollywood celebrity]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: relationshipToFame
Context triple: [Blanche Hudson, relationshipToFame, former Hollywood celebrity]
  • A. organFamousFor
    Indicates that an organ is widely recognized or notable for a particular characteristic, function, or association.
  • B. fameFor
    Indicates that one entity is widely known or recognized specifically because of, or in connection with, another entity.
  • C. famousIndividual chosen
    Indicates that an individual is widely known and recognized by a large number of people, typically for notable achievements, status, or public visibility.
  • D. namedForNotablePersonFrom
    Indicates that one entity is named in honor of a notable person who originates from another specified place or group.
  • E. namedForKnownFor
    Indicates that one entity is named after another entity specifically because that other entity is notable or recognized for something.
  • F. None of above.

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_69e0c45c81f08190a6b8bbb70a45aae7 completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69e9ea863b18819080e3ff249b10ec28 completed April 23, 2026, 9:46 a.m.
PD Predicate disambiguation batch_69e631f6e68081908f5ee4ce7413803e completed April 20, 2026, 2:02 p.m.
Created at: April 16, 2026, 6:25 p.m.