Triple
T17729507
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Superstrat guitars |
E442549
|
entity |
| Predicate | typicalNeckConstruction |
P49300
|
FINISHED |
| Object | bolt-on neck |
—
|
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: bolt-on neck | Statement: [Superstrat guitars, typicalNeckConstruction, bolt-on neck]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalNeckConstruction Context triple: [Superstrat guitars, typicalNeckConstruction, bolt-on neck]
-
A.
neckCharacteristic
chosen
Indicates that an entity has a specific attribute, feature, or quality related to its neck.
-
B.
hasNeckWood
Indicates that one entity uses or features a particular type of wood for its neck component.
-
C.
hasTypicalSleeveStyle
Indicates the usual or characteristic sleeve design associated with an item, such as a garment or uniform.
-
D.
typicalShoulderLine
Indicates that one entity has a shoulder line that is characteristic or standard for the type, style, or category represented by the other entity.
-
E.
neckLengthComparedTo
Indicates a comparison of the length of one entity’s neck relative to another entity’s neck.
- 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.