Triple

T23979305
Position Surface form Disambiguated ID Type / Status
Subject Cora Corman E604460 entity
Predicate fictionalManagement P86010 FINISHED
Object music industry handlers 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: music industry handlers | Statement: [Cora Corman, fictionalManagement, music industry handlers]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: fictionalManagement
Context triple: [Cora Corman, fictionalManagement, music industry handlers]
  • A. fictionalManager chosen
    Indicates that one entity serves as the (possibly invented or non-real) manager of another entity.
  • B. fictionalMandate
    Indicates that an entity is required or obligated to act according to rules, authority, or conditions that exist only within a fictional or imagined context.
  • C. fictionalField
    Indicates that the subject is associated with a fictional or imaginary field, domain, or area rather than a real-world one.
  • D. fictionalAgency
    Indicates a relationship in which an entity is associated with, created by, or operating under an organization that exists only within a fictional or imaginary context.
  • E. fictionalFocus
    Indicates that the primary emphasis or attention within a context is placed on fictional content, elements, or aspects.
  • 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_69e29543f40c819087700b7a272afb60 completed April 17, 2026, 8:17 p.m.
NER Named-entity recognition batch_69f1d2bc79688190bc98a2d57b91f5a3 completed April 29, 2026, 9:43 a.m.
PD Predicate disambiguation batch_69f161578d54819084a8b35496299993 completed April 29, 2026, 1:39 a.m.
Created at: April 17, 2026, 9:27 p.m.