Triple
T17729483
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Superstrat guitars |
E442549
|
entity |
| Predicate | typicalFingerboardRadius |
P61827
|
FINISHED |
| Object | flat or compound radius |
—
|
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: flat or compound radius | Statement: [Superstrat guitars, typicalFingerboardRadius, flat or compound radius]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalFingerboardRadius Context triple: [Superstrat guitars, typicalFingerboardRadius, flat or compound radius]
-
A.
fingerboardRadius
chosen
Indicates the curvature radius of a fingerboard, describing how rounded or flat it is across its width.
-
B.
hasFingerboardWood
Indicates that one entity uses or features the other as the material of its fingerboard.
-
C.
hasFingeringSystem
Indicates that an instrument or object is associated with a particular method or system for positioning fingers to produce notes or actions.
-
D.
hasFrets
Indicates that an instrument or similar object possesses frets, i.e., raised elements on its neck or surface that divide it into fixed pitch intervals.
-
E.
fretType
Indicates the specific style or configuration of frets used in relation to an instrument or fretboard.
- 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_69d8b9ec79688190b86bdcef85a7b3aa |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e478e5ba7c81908f8b06eb6859067f |
completed | April 19, 2026, 6:40 a.m. |
| PD | Predicate disambiguation | batch_69e3cde815e08190881972e2d80d151e |
completed | April 18, 2026, 6:31 p.m. |
Created at: April 10, 2026, 10:08 a.m.