Triple
T38114761
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Poison |
E951758
|
entity |
| Predicate | parentFragranceLine |
P46923
|
FINISHED |
| Object | Dior Poison collection |
—
|
NE NERFINISHED |
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: Dior Poison collection | Statement: [Poison, parentFragranceLine, Dior Poison collection]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parentFragranceLine Context triple: [Poison, parentFragranceLine, Dior Poison collection]
-
A.
hasFragranceLine
chosen
Indicates that one entity (typically a brand or company) offers or is associated with a particular line or collection of fragrances.
-
B.
hasFragrance
Indicates that one entity possesses or emits a particular scent or aroma associated with another entity.
-
C.
parentBrand
Indicates that one brand is the overarching or owning brand from which another brand is derived or subordinated.
-
D.
hasFragranceForm
Indicates that an entity has a specific form or type of fragrance it is associated with or presented in.
-
E.
hasFragranceIndustry
Indicates that an entity is involved in, associated with, or possesses a fragrance-related industry or business activity.
- 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_69f76f07734c8190814e937e12257a78 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fe86cad5108190b0164b8bc6fc23ea |
completed | May 9, 2026, 12:58 a.m. |
| PD | Predicate disambiguation | batch_69fe83c0c9888190b6fc40c7f727b569 |
completed | May 9, 2026, 12:45 a.m. |
Created at: May 3, 2026, 4:21 p.m.