Triple

T9379372
Position Surface form Disambiguated ID Type / Status
Subject Be Cool E225741 entity
Predicate hasCreativeWorkStatus P88612 FINISHED
Object released 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: released | Statement: [Be Cool, hasCreativeWorkStatus, released]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasCreativeWorkStatus
Context triple: [Be Cool, hasCreativeWorkStatus, released]
  • A. hasCatalogedWorkOn
    Indicates that an entity has formally recorded, listed, or documented another entity as a work within a catalog or collection.
  • B. hasWorksAbout
    Indicates that one entity (such as a creator, collection, or source) includes or is associated with works whose subject or focus is another entity.
  • C. hasWorkStatus
    Indicates the current employment or occupational state associated with an entity, such as whether it is active, inactive, or in a specific work condition.
  • D. hasWrittenWorkType
    Indicates that an entity (typically a written work) is associated with a specific type or category of written work (such as novel, article, report, etc.).
  • E. authorshipStatus
    Indicates the current state or condition of an entity’s role as an author in relation to a work (e.g., confirmed, disputed, anonymous, or pending).
  • 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_69ca842d8ee88190aaaa639aa953185d completed March 30, 2026, 2:09 p.m.
NER Named-entity recognition batch_69cd50bb49bc8190bdad23e120755ac7 completed April 1, 2026, 5:07 p.m.
PD Predicate disambiguation batch_69cca53bd6ec81909bf403ce304e5c08 completed April 1, 2026, 4:55 a.m.
PDg Predicate description generation batch_69cca89b3368819087a3d69270c1f185 completed April 1, 2026, 5:09 a.m.
Created at: March 30, 2026, 7:44 p.m.