Triple
T31659660
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Down Home Blues |
E807963
|
entity |
| Predicate | hasElectricInstrumentation |
P180353
|
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: [Down Home Blues, hasElectricInstrumentation, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasElectricInstrumentation Context triple: [Down Home Blues, hasElectricInstrumentation, true]
-
A.
hasInstrumentationProvidedBy
Indicates that the instrumentation used in an activity, process, or work is supplied or made available by a specified provider.
-
B.
supportsDynamicInstrumentation
Indicates that an entity is capable of being instrumented or monitored at runtime without requiring recompilation or restart.
-
C.
hasMinimalInstrumentation
Indicates that an entity is associated with or characterized by using the smallest necessary amount of instrumentation or equipment.
-
D.
usesInstrument
Indicates that an agent performs an action by employing a specific instrument or tool as the means to carry it out.
-
E.
hasInstrumentClass
Indicates that an action or process is carried out using an instrument that belongs to a specified class or category of instruments.
- 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_69f348daf95c81908b4c985b7ddcd0b3 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f73ae120bc8190bff94d38d7a7a00d |
completed | May 3, 2026, 12:09 p.m. |
| PD | Predicate disambiguation | batch_69f73a38d0848190aa5139144b8561c6 |
completed | May 3, 2026, 12:06 p.m. |
| PDg | Predicate description generation | batch_69f73adfd9a081908adae6bd59dfefb9 |
completed | May 3, 2026, 12:09 p.m. |
Created at: April 30, 2026, 10:56 p.m.