Triple
T5628433
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fender Telecaster |
E147775
|
entity |
| Predicate | standardTuning |
P30142
|
FINISHED |
| Object | E A D G B E |
—
|
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: E A D G B E | Statement: [Fender Telecaster, standardTuning, E A D G B E]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardTuning Context triple: [Fender Telecaster, standardTuning, E A D G B E]
-
A.
tuningOfInstrument
chosen
Indicates the specific tuning configuration or pitch arrangement applied to a musical instrument.
-
B.
typicalNotation
Indicates that one entity is the standard or commonly used symbolic representation (notation) for another entity.
-
C.
tuning
Indicates the adjustment or calibration of something’s parameters or settings to achieve desired performance or behavior.
-
D.
baseStandard
Indicates that one entity serves as the foundational or reference standard upon which another entity is defined, measured, or evaluated.
-
E.
tonalCenter
Indicates that one musical element functions as the primary pitch or key center around which another musical element is organized.
- 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_69c00906f2a88190a992c66b13d606d4 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c0223b1e54819099fe5fc84ed17a88 |
completed | March 22, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69c01b1d4b108190846ce586dc783acf |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:40 p.m.