Triple
T9288229
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kir |
E223450
|
entity |
| Predicate | typicalServingOccasion |
P14787
|
FINISHED |
| Object | before meals |
—
|
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: before meals | Statement: [Kir, typicalServingOccasion, before meals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalServingOccasion Context triple: [Kir, typicalServingOccasion, before meals]
-
A.
servingOccasion
chosen
Indicates the occasion, event, or context during which something (typically food or drink) is served.
-
B.
primaryOccasion
Indicates that one occasion is the main or most significant event associated with a given context, entity, or activity.
-
C.
suitableOccasion
Indicates that a particular occasion or context is appropriate or fitting for a given entity, action, or event.
-
D.
targetOccasion
Indicates the specific event, situation, or occasion toward which an action, plan, or intention is directed.
-
E.
usedOnOccasions
Indicates that something is employed or utilized during specific events, times, or circumstances rather than continuously.
- 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_69ca8422ddf881908a3f8f876c9f53aa |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd0862b34c819097cb7c1777313925 |
completed | April 1, 2026, 11:58 a.m. |
| PD | Predicate disambiguation | batch_69cc7a5aeb748190afb89c6bbd2a6d6f |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:35 p.m.