Triple
T7402841
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Libre (fragrance) |
E170789
|
entity |
| Predicate | bottleDesignFeature |
P64696
|
FINISHED |
| Object | bent gold Cassandra YSL logo |
—
|
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: bent gold Cassandra YSL logo | Statement: [Libre (fragrance), bottleDesignFeature, bent gold Cassandra YSL logo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bottleDesignFeature Context triple: [Libre (fragrance), bottleDesignFeature, bent gold Cassandra YSL logo]
-
A.
bottleFeature
chosen
Indicates that a bottle possesses or is characterized by a particular feature or attribute.
-
B.
hasBottleColor
Indicates that an entity is associated with a bottle characterized by a specific color.
-
C.
designedFeature
Indicates that one entity is a feature or component intentionally planned, created, or specified by another entity as part of a design.
-
D.
featuresBeverage
Indicates that one entity includes, offers, or presents a particular beverage as part of its contents, services, or characteristics.
-
E.
designedWith
Indicates that one entity was created, planned, or developed using another entity as a tool, method, or guiding basis in its design process.
- 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_69c68a6010108190925e5284de022660 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f26ea27c8190a55e0e0314b463d8 |
completed | March 27, 2026, 9:11 p.m. |
| PD | Predicate disambiguation | batch_69c6f0323b2c819098ab72c33e6d8534 |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:10 p.m.