Triple
T30933040
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World's Best Boss mug |
E788045
|
entity |
| Predicate | typicalPurchaseOccasion |
P89869
|
FINISHED |
| Object | Father's Day gifts |
—
|
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: Father's Day gifts | Statement: [World's Best Boss mug, typicalPurchaseOccasion, Father's Day gifts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalPurchaseOccasion Context triple: [World's Best Boss mug, typicalPurchaseOccasion, Father's Day gifts]
-
A.
primaryOccasion
Indicates that one occasion is the main or most significant event associated with a given context, entity, or activity.
-
B.
creationOccasion
Indicates the specific event, context, or circumstances during which something was created.
-
C.
targetOccasion
Indicates the specific event, situation, or occasion toward which an action, plan, or intention is directed.
-
D.
usedOnOccasions
Indicates that something is employed or utilized during specific events, times, or circumstances rather than continuously.
-
E.
occasionType
chosen
Indicates the specific kind or category of occasion or event associated with the subject.
- 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_69f224c0b7fc819090cb89df60d23653 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e2fac0819089b522db3260028c |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 8:52 p.m.