Triple
T32434549
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gibson ES-335 |
E828819
|
entity |
| Predicate | hasEpiphoneVersion |
P174083
|
FINISHED |
| Object | Epiphone Dot |
—
|
NE NERFINISHED |
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: Epiphone Dot | Statement: [Gibson ES-335, hasEpiphoneVersion, Epiphone Dot]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEpiphoneVersion Context triple: [Gibson ES-335, hasEpiphoneVersion, Epiphone Dot]
-
A.
hasElectricGuitar
Indicates that an entity possesses or is associated with an electric guitar.
-
B.
usesElectricGuitar
Indicates that an entity performs, creates, or is associated with an action or role that involves playing or employing an electric guitar.
-
C.
hasSteelGuitar
Indicates that one entity possesses, includes, or features a steel guitar in relation to another entity or context.
-
D.
hasGuitarEffect
Indicates that one entity applies, uses, or is associated with a particular guitar effect in relation to another entity.
-
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. 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_69f3491bf298819097b610f772d54a6d |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c2b0d31c8190adb202fdf21d4797 |
completed | May 3, 2026, 3:36 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6eb32c8190bf405b2011fa48f7 |
completed | May 3, 2026, 3:01 a.m. |
| PDg | Predicate description generation | batch_69f6bb344bb48190a8089f29c0063ded |
completed | May 3, 2026, 3:04 a.m. |
Created at: May 1, 2026, 12:55 a.m.