Triple

T23927816
Position Surface form Disambiguated ID Type / Status
Subject therealdebramessing E602406 entity
Predicate knownForFeaturing P154391 FINISHED
Object Debra Messing’s professional work 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: Debra Messing’s professional work | Statement: [therealdebramessing, knownForFeaturing, Debra Messing’s professional work]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: knownForFeaturing
Context triple: [therealdebramessing, knownForFeaturing, Debra Messing’s professional work]
  • A. segmentKnownFor
    Indicates that a specific segment or portion of something is recognized or notable for a particular characteristic, feature, or association.
  • B. namedForKnownFor
    Indicates that one entity is named after another entity specifically because that other entity is notable or recognized for something.
  • C. knownForAct
    Indicates that an entity is recognized or notable for performing a particular act or action.
  • D. knownForCollectionOf
    Indicates that one entity is recognized or notable specifically for its collection or assemblage of another type of entity.
  • E. nowKnownFor
    Indicates that an entity is currently recognized or notable for a particular role, attribute, achievement, or association.
  • 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_69e2953b928c819095395fa87baca583 completed April 17, 2026, 8:16 p.m.
NER Named-entity recognition batch_69f1cf1efb348190b4cbb32b3b6c9ae4 completed April 29, 2026, 9:27 a.m.
PD Predicate disambiguation batch_69f16151ebdc819086e9e1d7cc1f4f3c completed April 29, 2026, 1:39 a.m.
PDg Predicate description generation batch_69f16e348b548190b76e50f9b611f76d completed April 29, 2026, 2:34 a.m.
Created at: April 17, 2026, 8:49 p.m.