Triple

T9642067
Position Surface form Disambiguated ID Type / Status
Subject Symphony No. 8 in D minor E233095 entity
Predicate scoringDetail P89407 FINISHED
Object large orchestra with extensive percussion — 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: large orchestra with extensive percussion | Statement: [Symphony No. 8 in D minor, scoringDetail, large orchestra with extensive percussion]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: scoringDetail
Context triple: [Symphony No. 8 in D minor, scoringDetail, large orchestra with extensive percussion]
  • A. individualScoring
    Indicates that a specific individual receives or is assigned a particular score or evaluation in a given context.
  • B. scoring
    Indicates the act of achieving points or a measurable result, typically by successfully completing an action that contributes to a score or outcome.
  • C. scoringRecord
    Indicates that there exists a record documenting a scoring event or outcome associated with the given entities.
  • D. scoringType
    Indicates the method or criteria by which performance, outcomes, or results are evaluated and assigned a score in a given context.
  • E. scoringUnit
    Indicates that one entity functions as a unit or component responsible for scoring or assigning scores to another entity.
  • 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_69ca848a5a908190aad251f4137b0c3a completed March 30, 2026, 2:11 p.m.
NER Named-entity recognition batch_69cd9b566a2881909ab3f9502b1c3c8d completed April 1, 2026, 10:25 p.m.
PD Predicate disambiguation batch_69ccd5b0263081908cf6df3eb07d71b0 completed April 1, 2026, 8:22 a.m.
PDg Predicate description generation batch_69ccd93fc45c8190a823305e461e581d completed April 1, 2026, 8:37 a.m.
Created at: March 30, 2026, 8:12 p.m.