Triple
T37505568
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Light That Blinds |
E932079
|
entity |
| Predicate | hasProminentTechniques |
P51617
|
FINISHED |
| Object | twin-guitar harmonies |
—
|
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: twin-guitar harmonies | Statement: [The Light That Blinds, hasProminentTechniques, twin-guitar harmonies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProminentTechniques Context triple: [The Light That Blinds, hasProminentTechniques, twin-guitar harmonies]
-
A.
hasTechnique
Indicates that an entity employs, utilizes, or is associated with a particular method, procedure, or technique.
-
B.
featuresTechnique
chosen
Indicates that something incorporates or makes use of a particular technique as part of its content or execution.
-
C.
demonstratedTechniqueFocus
Indicates that an entity has shown or highlighted a particular technique as the main focus of its demonstration.
-
D.
hasDistinctiveTechnology
Indicates that an entity possesses a unique or distinguishing technology that sets it apart from others.
-
E.
allowedTechnique
Indicates that a particular technique or method is permitted or acceptable to use in a given context or under specified rules.
- 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_69f76ec5268481909ea01c73aeeefd42 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a1553e08190bb7424c448cb1f33 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:17 p.m.