Triple
T23714965
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Angry Chair |
E585972
|
entity |
| Predicate | usesGuitarTuning |
P30142
|
FINISHED |
| Object | down-tuned guitars |
—
|
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: down-tuned guitars | Statement: [Angry Chair, usesGuitarTuning, down-tuned guitars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesGuitarTuning Context triple: [Angry Chair, usesGuitarTuning, down-tuned guitars]
-
A.
usesAcousticGuitar
Indicates that one entity plays, performs with, or otherwise employs an acoustic guitar in an action or context involving another entity.
-
B.
usesTuneOf
Indicates that one work is created to be performed with, or is based on, the melody or musical setting originally belonging to another work.
-
C.
tuningOfInstrument
chosen
Indicates the specific tuning configuration or pitch arrangement applied to a musical instrument.
-
D.
usesElectricGuitar
Indicates that an entity performs, creates, or is associated with an action or role that involves playing or employing an electric guitar.
-
E.
tunedOrUntuned
Indicates whether something is in a properly adjusted or calibrated state (tuned) or not (untuned).
- 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_69e24905f77881908194d645676acd60 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b779f8508190a0a7f5496252b471 |
completed | April 29, 2026, 7:47 a.m. |
| PD | Predicate disambiguation | batch_69f155e4b1148190836ede4741dcb888 |
completed | April 29, 2026, 12:50 a.m. |
Created at: April 17, 2026, 6:54 p.m.