Triple
T19913825
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 18 til I Die |
E478612
|
entity |
| Predicate | containsGuitarDrivenSound |
P103934
|
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: [18 til I Die, containsGuitarDrivenSound, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsGuitarDrivenSound Context triple: [18 til I Die, containsGuitarDrivenSound, true]
-
A.
isGuitarDriven
chosen
Indicates that something (such as a song, piece of music, or performance) is primarily led, dominated, or characterized by the sound and role of the guitar.
-
B.
hasGuitarEffect
Indicates that one entity applies, uses, or is associated with a particular guitar effect in relation to another entity.
-
C.
containsSound
Indicates that one entity includes, embodies, or produces the sound associated with another entity.
-
D.
hasGuitarRiffs
Indicates that one entity features or contains guitar riffs provided or performed by another entity.
-
E.
hasGuitarStyle
Indicates that an entity is associated with, characterized by, or performs using a particular style of guitar playing.
- 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_69d8e520682081909892916424699bd5 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e659928030819085a4aafc6a0ef5c8 |
completed | April 20, 2026, 4:51 p.m. |
| PD | Predicate disambiguation | batch_69e537ecda248190895c96afb6243823 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:53 p.m.