Triple
T36271422
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OM (Orchestra Model) guitar |
E892683
|
entity |
| Predicate | typicalScaleLengthInMillimeters |
P128778
|
FINISHED |
| Object | 645 |
—
|
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: 645 | Statement: [OM (Orchestra Model) guitar, typicalScaleLengthInMillimeters, 645]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalScaleLengthInMillimeters Context triple: [OM (Orchestra Model) guitar, typicalScaleLengthInMillimeters, 645]
-
A.
typicalScaleLength
chosen
Indicates the characteristic or standard length scale that typically applies to the entity or phenomenon in question.
-
B.
typicalTrackLengthRange
Indicates the usual minimum and maximum lengths that a track associated with something tends to fall between.
-
C.
numberOfFrets
Indicates the specific count of frets associated with an instrument or fretboard.
-
D.
typicalLength
Indicates the usual or characteristic length associated with an entity or phenomenon.
-
E.
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.
- 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_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0a54cc8190868c1bfa1590d1a6 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:09 p.m.