Triple
T22130365
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Unforgiven |
E546888
|
entity |
| Predicate | openingInstrument |
P12878
|
FINISHED |
| Object | acoustic guitar |
—
|
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: acoustic guitar | Statement: [The Unforgiven, openingInstrument, acoustic guitar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openingInstrument Context triple: [The Unforgiven, openingInstrument, acoustic guitar]
-
A.
parentInstrument
Indicates that one instrument serves as the broader, containing, or originating instrument from which another, more specific or derived instrument is related.
-
B.
introducedInstrument
Indicates that one entity caused or brought about the initial use or adoption of a particular instrument by another entity or within a given context.
-
C.
allowedInstrument
Indicates that a particular instrument is permitted or authorized for use in a given context or activity.
-
D.
hostInstrument
Indicates that one entity serves as the instrument or platform that hosts, carries, or enables another entity or process.
-
E.
musicInstrumentation
chosen
Indicates the specific instruments or instrumental forces used to perform a piece of music.
- 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_69e11e39bf348190b541bfa16a7b71e0 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f129851db8819082d50bbb73670bf6 |
completed | April 28, 2026, 9:41 p.m. |
| PD | Predicate disambiguation | batch_69e71b384e008190b723c9a0f1089d66 |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:32 p.m.