Triple
T8536663
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eternity (fragrance) |
E202092
|
entity |
| Predicate | hasSillageReputation |
P83196
|
FINISHED |
| Object | moderate |
—
|
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: moderate | Statement: [Eternity (fragrance), hasSillageReputation, moderate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSillageReputation Context triple: [Eternity (fragrance), hasSillageReputation, moderate]
-
A.
hasReputationAmong
Indicates that an entity is regarded or perceived in a particular way by a specified group or audience.
-
B.
hasQuirkyReputation
Indicates that an entity is regarded by others as having an unusual, eccentric, or unconventional character or style.
-
C.
hasNotableReputation
Indicates that an entity is widely recognized or distinguished for a particular quality, achievement, or characteristic.
-
D.
associatedWithReputation
Indicates a relationship where an entity is linked to, influenced by, or characterized in terms of another entity’s reputation or perceived standing.
-
E.
denotesReputationOf
Indicates that one entity represents, expresses, or serves as an indicator of the reputation or perceived standing of another entity.
- 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_69ca832355b08190b8b6a4ab4a4a3554 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe6a3f024819095d560a205ff1c75 |
completed | March 31, 2026, 3:22 p.m. |
| PD | Predicate disambiguation | batch_69cbd111bf988190be98c92a607c6456 |
completed | March 31, 2026, 1:50 p.m. |
| PDg | Predicate description generation | batch_69cbe30d453481908f897ed2b06e7534 |
completed | March 31, 2026, 3:06 p.m. |
Created at: March 30, 2026, 6:18 p.m.