Triple
T26310681
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Black Opium Neon |
E661810
|
entity |
| Predicate | coreDNA |
P110510
|
FINISHED |
| Object | Black Opium coffee-vanilla accord |
—
|
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: Black Opium coffee-vanilla accord | Statement: [Black Opium Neon, coreDNA, Black Opium coffee-vanilla accord]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coreDNA Context triple: [Black Opium Neon, coreDNA, Black Opium coffee-vanilla accord]
-
A.
coreFusion
Indicates a relationship where two or more central or fundamental components are merged into a single unified core.
-
B.
core
chosen
Indicates a central, most important, or foundational part of something in relation to its surrounding or supporting elements.
-
C.
coreModule
Indicates that something functions as a primary or foundational module within a larger system or structure.
-
D.
coreHolding
Indicates a primary or central ownership relationship where one entity holds a significant, foundational stake or position in another.
-
E.
geneticMaterial
Indicates that one entity serves as the hereditary or genetic substance (e.g., DNA or RNA) of another entity.
- 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_69ee812dacfc81908484aade9120fba9 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f60ee7e6348190951e6f9647f5555b |
completed | May 2, 2026, 2:49 p.m. |
| PD | Predicate disambiguation | batch_69f5f7ff548c8190a23e98c5e66e0bc7 |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 26, 2026, 10:22 p.m.