Triple

T29789977
Position Surface form Disambiguated ID Type / Status
Subject E major E756375 entity
Predicate usedForTuningReference P98657 FINISHED
Object guitar standard tuning open 1st string 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: guitar standard tuning open 1st string | Statement: [E major, usedForTuningReference, guitar standard tuning open 1st string]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usedForTuningReference
Context triple: [E major, usedForTuningReference, guitar standard tuning open 1st string]
  • A. usesTuningReference
    Indicates that one entity adopts another entity as the pitch or frequency standard for tuning.
  • B. usedTuningSystem
    Indicates that an entity (such as a musical work, performance, or instrument) employs or is based on a particular tuning system.
  • C. usedToCalibrate chosen
    Indicates that one entity serves as a reference or standard to adjust, tune, or verify the accuracy of another entity.
  • D. usedReferenceFrame
    Indicates that one entity adopts or relies on another entity as the coordinate system or reference frame for describing positions, motions, or measurements.
  • E. tuningMethod
    Indicates the method or approach used to adjust or optimize something’s parameters or performance.
  • 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_69f22451fb748190bbdbab401280affb completed April 29, 2026, 3:31 p.m.
NER Named-entity recognition batch_69f74062b9388190b30546cf700a825c completed May 3, 2026, 12:32 p.m.
PD Predicate disambiguation batch_69f73c802b848190b61a416b7488bd96 completed May 3, 2026, 12:16 p.m.
Created at: April 29, 2026, 5:12 p.m.