Triple
T12742593
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Slivovitz |
E304523
|
entity |
| Predicate | isUsedOnOccasion |
P37361
|
FINISHED |
| Object | weddings |
—
|
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: weddings | Statement: [Slivovitz, isUsedOnOccasion, weddings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isUsedOnOccasion Context triple: [Slivovitz, isUsedOnOccasion, weddings]
-
A.
usedOnOccasions
chosen
Indicates that something is employed or utilized during specific events, times, or circumstances rather than continuously.
-
B.
onOccasionOf
Indicates that one event, action, or state occurs in connection with, or is triggered by, a particular occasion or special event.
-
C.
createdOnOccasionOf
Indicates that something was created specifically for, or in direct connection with, a particular event, occasion, or circumstance.
-
D.
hasOccasionType
Indicates that an occasion, event, or happening is classified as being of a particular type or category.
-
E.
frequentOccasion
Indicates that a particular event, situation, or condition occurs repeatedly or commonly over time.
- 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_69d7bdf1426c8190a4402e1c4cdec33a |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96d89ea70819098c470344f172167 |
completed | April 10, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69d96406e97c8190b79081039847115c |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:26 p.m.