Triple
T34087316
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ernest Beaux |
E874207
|
entity |
| Predicate | createdFragrance |
P199447
|
FINISHED |
| Object | Chanel No. 5 |
—
|
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: Chanel No. 5 | Statement: [Ernest Beaux, createdFragrance, Chanel No. 5]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: createdFragrance Context triple: [Ernest Beaux, createdFragrance, Chanel No. 5]
-
A.
createdFragranceFor
Indicates that one entity designed or produced a fragrance specifically for another entity.
-
B.
launchedPerfume
Indicates that an entity has introduced or released a perfume product to the market.
-
C.
fragranceInspiration
Indicates that one entity serves as the creative or conceptual inspiration behind the fragrance of another entity.
-
D.
hasFragrance
Indicates that one entity possesses or emits a particular scent or aroma associated with another entity.
-
E.
hasFragranceForm
Indicates that an entity has a specific form or type of fragrance it is associated with or presented in.
- 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_69f349a61d448190b74642f325d3eb7a |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff397e19a88190a945b826159f5290 |
completed | May 9, 2026, 1:41 p.m. |
| PD | Predicate disambiguation | batch_69ff392400d0819088d30d08d4a774bd |
completed | May 9, 2026, 1:39 p.m. |
| PDg | Predicate description generation | batch_69ff397d6a2081908fa8f62e8902421b |
completed | May 9, 2026, 1:41 p.m. |
Created at: May 1, 2026, 1:52 a.m.