Triple
T11069765
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gibson ES-355 |
E261713
|
entity |
| Predicate | positionRelativeToES335 |
P97634
|
FINISHED |
| Object | more ornate and upscale |
—
|
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: more ornate and upscale | Statement: [Gibson ES-355, positionRelativeToES335, more ornate and upscale]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionRelativeToES335 Context triple: [Gibson ES-355, positionRelativeToES335, more ornate and upscale]
-
A.
positionOnInstruments
Indicates the specific role or seat an individual holds within a group of instruments, such as in an orchestra or ensemble.
-
B.
positionOnSpectrum
Indicates the relative location or value of something along a defined continuum or range of possible states.
-
C.
positionInBand
Indicates the specific role or place an individual holds within a musical band.
-
D.
numberOfFrets
Indicates the specific count of frets associated with an instrument or fretboard.
-
E.
locationRelativeToPitch
Indicates the spatial position of an entity in relation to the pitch (e.g., above, beside, or within the pitch area).
- 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_69d6aa9983c08190b0ef61603b69feac |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d799221e848190b0f86ae3eb5e3e02 |
completed | April 9, 2026, 12:18 p.m. |
| PD | Predicate disambiguation | batch_69d74411d9e881908c0eeafa0f38e4b6 |
completed | April 9, 2026, 6:15 a.m. |
| PDg | Predicate description generation | batch_69d750c99f9881908ee2b01b6ce4b3a1 |
completed | April 9, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:26 p.m.