Triple

T33201645
Position Surface form Disambiguated ID Type / Status
Subject Pachchai Nirame E849913 entity
Predicate originalScoreContext P199653 FINISHED
Object romantic drama film 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: romantic drama film | Statement: [Pachchai Nirame, originalScoreContext, romantic drama film]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: originalScoreContext
Context triple: [Pachchai Nirame, originalScoreContext, romantic drama film]
  • A. scoringRecordContext
    Indicates the situational or contextual factors under which a scoring event or record occurs.
  • B. hasOriginalScoreFor chosen
    Indicates that one entity is the original musical score specifically composed for another entity, such as a film, show, or performance.
  • C. scoringInOriginalUse
    Indicates that an entity is performing a scoring action within its initial or primary context of use, rather than in a derived or subsequent context.
  • D. scoring
    Indicates the act of achieving points or a measurable result, typically by successfully completing an action that contributes to a score or outcome.
  • E. featuresOriginalScore
    Indicates that an entity includes or is accompanied by its initial, unaltered score or musical composition.
  • 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_69f3495efedc8190843a5728089544b9 completed April 30, 2026, 12:21 p.m.
NER Named-entity recognition batch_6a02f2d6f35481909829d4ec710dcb0f completed May 12, 2026, 9:28 a.m.
PD Predicate disambiguation batch_6a02f15a2460819080cb4be5b50221d0 completed May 12, 2026, 9:22 a.m.
Created at: May 1, 2026, 1:30 a.m.