Triple
T36271457
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OM (Orchestra Model) guitar |
E892683
|
entity |
| Predicate | hasSoundholeShape |
P91630
|
FINISHED |
| Object | round |
—
|
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: round | Statement: [OM (Orchestra Model) guitar, hasSoundholeShape, round]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSoundholeShape Context triple: [OM (Orchestra Model) guitar, hasSoundholeShape, round]
-
A.
hasSoundHole
Indicates that one entity possesses or features a sound hole as a characteristic or component.
-
B.
headstockShape
Indicates the specific contour or outline form of an object’s headstock relative to other parts or designs.
-
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.
hasHoleShape
chosen
Indicates that an entity possesses a hole or opening characterized by a specific geometric or structural shape.
-
E.
hasUnpolishedSound
Indicates that something produces or exhibits a rough, raw, or unrefined sound quality.
- 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_69f76e488f34819083e254dbe288c27a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fd7fdafbe881908a31fcb407af2c34 |
completed | May 8, 2026, 6:16 a.m. |
| PD | Predicate disambiguation | batch_69fd7ef0ea908190b5d83f71565bdb1c |
completed | May 8, 2026, 6:13 a.m. |
Created at: May 3, 2026, 4:09 p.m.