Triple

T8892996
Position Surface form Disambiguated ID Type / Status
Subject Long Ago and Far Away E211726 entity
Predicate hasExpressiveStyle P70301 FINISHED
Object expressive 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: expressive | Statement: [Long Ago and Far Away, hasExpressiveStyle, expressive]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasExpressiveStyle
Context triple: [Long Ago and Far Away, hasExpressiveStyle, expressive]
  • A. hasExpressivity
    Indicates that one entity possesses a certain level or type of expressive power, capability, or richness in representation relative to another.
  • B. hasExpressiveRole
    Indicates that an entity serves a communicative or expressive function or role in relation to another entity or context.
  • C. hasDramaticStyle
    Indicates that an entity employs or is characterized by a theatrical, emotionally intense, or striking manner of expression or presentation.
  • D. moreExpressiveThan
    Indicates that one entity conveys ideas, emotions, or information with greater richness, nuance, or clarity than another.
  • E. expressiveQuality chosen
    Indicates the distinctive emotional or stylistic character conveyed by something, such as how it feels, sounds, or appears in an expressive sense.
  • 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_69ca83907954819096d52a245b635841 completed March 30, 2026, 2:07 p.m.
NER Named-entity recognition batch_69cc61bb46c881909e579bb1926e5204 completed April 1, 2026, 12:07 a.m.
PD Predicate disambiguation batch_69cc5c2aec04819093c932fe51c0f08d completed March 31, 2026, 11:43 p.m.
Created at: March 30, 2026, 6:54 p.m.