Triple
T29218741
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rickenbacker 4001 |
E740750
|
entity |
| Predicate | fingerboardInlays |
P166437
|
FINISHED |
| Object | triangle (sharkfin) inlays |
—
|
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: triangle (sharkfin) inlays | Statement: [Rickenbacker 4001, fingerboardInlays, triangle (sharkfin) inlays]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fingerboardInlays Context triple: [Rickenbacker 4001, fingerboardInlays, triangle (sharkfin) inlays]
-
A.
fingerboardRadius
Indicates the curvature radius of a fingerboard, describing how rounded or flat it is across its width.
-
B.
headstockInlay
Indicates that one entity is an inlay decoration located on the headstock of another entity (typically a stringed instrument).
-
C.
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.
-
D.
hasFingeringSystem
Indicates that an instrument or object is associated with a particular method or system for positioning fingers to produce notes or actions.
-
E.
fretMaterial
Indicates the material from which the frets of an instrument are made.
- 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_69f07cba2f808190a2746477d4e8345b |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f66430505481909c263d0b8f16309b |
completed | May 2, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f65c24f8b48190af81b575f3c15be5 |
completed | May 2, 2026, 8:18 p.m. |
| PDg | Predicate description generation | batch_69f65fb2ead08190b06677d4d6ea1ea8 |
completed | May 2, 2026, 8:33 p.m. |
Created at: April 28, 2026, 12:14 p.m.