Triple

T13434117
Position Surface form Disambiguated ID Type / Status
Subject Cliff Huxtable E320184 entity
Predicate fictionalSpecialization P107007 FINISHED
Object obstetrics 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: obstetrics | Statement: [Cliff Huxtable, fictionalSpecialization, obstetrics]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: fictionalSpecialization
Context triple: [Cliff Huxtable, fictionalSpecialization, obstetrics]
  • A. fictionalMedium
    Indicates that a work of fiction is presented or conveyed through a particular medium or format (such as a book, film, game, or comic).
  • B. fictionalGenre
    Indicates that a work of fiction belongs to or is categorized under a particular narrative genre or style.
  • C. fictionalOrigin
    Indicates that one entity originates from, or was first introduced within, a fictional work, universe, or narrative created by another entity.
  • D. fictionalMaterial
    Indicates that something is made of, composed of, or incorporates a material that exists only in fiction or imagination.
  • E. hasFictionalSpecialization chosen
    Indicates that an entity’s area of focus, expertise, or role is within a fictional or imaginative domain rather than a real-world specialization.
  • 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_69d80761e6cc8190a90c844589998ecc completed April 9, 2026, 8:09 p.m.
NER Named-entity recognition batch_69dbaee29fec81908b07b4fca2922242 completed April 12, 2026, 2:40 p.m.
PD Predicate disambiguation batch_69d9a03926188190ab3948d1f5d3941f completed April 11, 2026, 1:13 a.m.
Created at: April 9, 2026, 9:40 p.m.