Triple

T22562446
Position Surface form Disambiguated ID Type / Status
Subject Symphony No. 5 (Arnold) E557850 entity
Predicate hasReceptionCharacteristic P274 FINISHED
Object regarded as powerful and intense 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: regarded as powerful and intense | Statement: [Symphony No. 5 (Arnold), hasReceptionCharacteristic, regarded as powerful and intense]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasReceptionCharacteristic
Context triple: [Symphony No. 5 (Arnold), hasReceptionCharacteristic, regarded as powerful and intense]
  • A. hasCharacteristic chosen
    Indicates that an entity possesses, exhibits, or is defined by a particular attribute, feature, or quality.
  • B. hasReception
    Indicates that an entity hosts, includes, or is associated with a reception event (such as a formal gathering or welcoming function).
  • C. hasReceiver
    Indicates that an entity serves as the recipient or target of something provided, sent, or directed by another entity.
  • D. eraCharacteristic
    Indicates that a particular quality, feature, or attribute is characteristic of, or typically associated with, a given historical or temporal era.
  • E. RRcCharacteristics
    Indicates that a resource or entity possesses specific characteristics, attributes, or properties associated with its RRc classification or role.
  • 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_69e11e5ae4ac8190b1f503457603d969 completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f15fa6a928819083925ea23aaaf725 completed April 29, 2026, 1:32 a.m.
PD Predicate disambiguation batch_69ee626e6bb08190ada4dd8b48cc0c43 completed April 26, 2026, 7:07 p.m.
Created at: April 16, 2026, 8:52 p.m.