Triple
T26310863
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Libre Le Parfum |
E661815
|
entity |
| Predicate | mainAccord |
P167081
|
FINISHED |
| Object | lavender |
—
|
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: lavender | Statement: [Libre Le Parfum, mainAccord, lavender]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainAccord Context triple: [Libre Le Parfum, mainAccord, lavender]
-
A.
mainAccessFor
Indicates that one entity serves as the primary means or route of access for another entity.
-
B.
mainCase
Indicates that one case is the primary or central case associated with an entity or context, distinguishing it from other related cases.
-
C.
mainRite
Indicates that one ritual, ceremony, or rite is the primary or central rite associated with a given context, entity, or event.
-
D.
primaryAccountIn
Indicates that an entity serves as the main or default account within a specified context, group, or container.
-
E.
mainClaim
Indicates that one statement is presented as the central or primary assertion being made about a topic.
- 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_69ee812dacfc81908484aade9120fba9 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f6653ccf648190b65fb1141928e47e |
completed | May 2, 2026, 8:57 p.m. |
| PD | Predicate disambiguation | batch_69f6633451948190bcc0410602bb4914 |
completed | May 2, 2026, 8:48 p.m. |
| PDg | Predicate description generation | batch_69f663ff176c8190aaadb475f75daee4 |
completed | May 2, 2026, 8:52 p.m. |
Created at: April 26, 2026, 10:22 p.m.