Triple
T17439035
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Get Your Shine On |
E424098
|
entity |
| Predicate | featuresElectricGuitar |
P98559
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Get Your Shine On, featuresElectricGuitar, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresElectricGuitar Context triple: [Get Your Shine On, featuresElectricGuitar, true]
-
A.
hasElectricGuitar
chosen
Indicates that an entity possesses or is associated with an electric guitar.
-
B.
featuresElectricSide
Indicates that something includes or is equipped with an electric-powered side or component as part of its design or functionality.
-
C.
hasGuitarEffect
Indicates that one entity applies, uses, or is associated with a particular guitar effect in relation to another entity.
-
D.
hasSteelGuitar
Indicates that one entity possesses, includes, or features a steel guitar in relation to another entity or context.
-
E.
notableInstrumentFeature
Indicates that an instrument is distinguished by a particular characteristic, quality, or component that is especially noteworthy or defining.
- 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_69d889d88b6081908bada047f5b3ba51 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e44ff584cc81908207c163f19ff972 |
completed | April 19, 2026, 3:45 a.m. |
| PD | Predicate disambiguation | batch_69e3b030eac481909b8402719cc3102e |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:46 a.m.