Triple
T30959971
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kare-Kare |
E788783
|
entity |
| Predicate | isCommonlyPreparedFor |
P102145
|
FINISHED |
| Object | family gatherings |
—
|
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: family gatherings | Statement: [Kare-Kare, isCommonlyPreparedFor, family gatherings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCommonlyPreparedFor Context triple: [Kare-Kare, isCommonlyPreparedFor, family gatherings]
-
A.
commonlyPreparedFor
chosen
Indicates that something is typically made, organized, or arranged in anticipation of a particular event, purpose, or recipient.
-
B.
typeOfPreparation
Indicates the method or process by which something is prepared or made ready for use, consumption, or further action.
-
C.
isOftenPreparedTableside
Indicates that the dish or item is frequently assembled, cooked, or finished in front of guests at their table rather than entirely in the kitchen.
-
D.
commonPreparationMethod
Indicates that two or more items share the same typical way of being prepared or processed.
-
E.
typicalPreparation
Indicates the usual or standard way in which something is prepared or made.
- 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_69f224c28c1881908c33b45d689f1724 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6cee45590819086e489bfccbe4ac3 |
completed | May 3, 2026, 4:28 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1188708190b8f0f56e595e6057 |
completed | May 3, 2026, 4:16 a.m. |
Created at: April 29, 2026, 8:54 p.m.