Triple
T22898293
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Painkiller cocktail |
E568235
|
entity |
| Predicate | isBlended |
P150168
|
FINISHED |
| Object | false |
—
|
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: false | Statement: [Painkiller cocktail, isBlended, false]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isBlended Context triple: [Painkiller cocktail, isBlended, false]
-
A.
oftenBlendedAs
Indicates that two or more entities are frequently mixed or combined together, typically to form a unified product or result.
-
B.
hasBlendOfOldAndNew
Indicates that something combines or integrates both traditional/older elements and modern/newer elements into a single whole.
-
C.
usedInBlends
Indicates that something serves as an ingredient or component within one or more mixtures, combinations, or blends.
-
D.
typicalBlendStyle
Indicates the usual or characteristic way in which two or more elements are combined or mixed together.
-
E.
hasMasterBlender
Indicates that one entity serves as the master blender (the primary expert responsible for blending) for another entity.
- 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_69e2458c23ec81908fa2570692c6614f |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1801415dc8190b5de6095f1ed4ba5 |
completed | April 29, 2026, 3:50 a.m. |
| PD | Predicate disambiguation | batch_69ef3b6b2e2481908258156937b5a745 |
completed | April 27, 2026, 10:33 a.m. |
| PDg | Predicate description generation | batch_69ef538a115081908982597f79355840 |
completed | April 27, 2026, 12:16 p.m. |
Created at: April 17, 2026, 3:41 p.m.