Triple
T2522401
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dolce & Gabbana The One |
E55552
|
entity |
| Predicate | topNote |
P39617
|
FINISHED |
| Object | bergamot |
—
|
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: bergamot | Statement: [Dolce & Gabbana The One, topNote, bergamot]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: topNote Context triple: [Dolce & Gabbana The One, topNote, bergamot]
-
A.
notableTrack
Indicates that a particular track (such as a song or recording) is especially significant, well-known, or prominent in relation to the subject.
-
B.
notableMistress
Indicates that a person is notably recognized as the mistress (non-marital romantic partner) of another person.
-
C.
notedIn
Indicates that information about one entity is mentioned, recorded, or referenced within another entity, such as a document, record, or source.
-
D.
notableSingle
Indicates that the subject is particularly recognized or distinguished for one specific, individual instance (such as a single work, event, or achievement).
-
E.
notableFavorite
Indicates that one entity is a particularly prominent or distinguished favorite of another entity compared to other possible favorites.
- 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_69ab49e4749c8190813311efd1630f1b |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abd23895348190bb4dad6d7174893a |
completed | March 7, 2026, 7:22 a.m. |
| PD | Predicate disambiguation | batch_69abd0c144b0819092f32a13c1d127e5 |
completed | March 7, 2026, 7:16 a.m. |
| PDg | Predicate description generation | batch_69abd1487e0c8190b90dcf30586ad4cd |
completed | March 7, 2026, 7:18 a.m. |
Created at: March 6, 2026, 9:46 p.m.