Triple
T32179833
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Qabili pulao |
E821949
|
entity |
| Predicate | typicallyServedOnOccasion |
P14787
|
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: [Qabili pulao, typicallyServedOnOccasion, weddings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicallyServedOnOccasion Context triple: [Qabili pulao, typicallyServedOnOccasion, weddings]
-
A.
servingOccasion
chosen
Indicates the occasion, event, or context during which something (typically food or drink) is served.
-
B.
usedOnOccasions
Indicates that something is employed or utilized during specific events, times, or circumstances rather than continuously.
-
C.
suitableOccasion
Indicates that a particular occasion or context is appropriate or fitting for a given entity, action, or event.
-
D.
occasionType
Indicates the specific kind or category of occasion or event associated with the subject.
-
E.
specialOccasion
Indicates that an event or situation is associated with a notable or exceptional occasion, such as a celebration, milestone, or culturally significant date.
- 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_69f3490755288190aee11740a34862f9 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379eaa540819095a1c5d9f3513f9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 12:34 a.m.