Triple
T14048663
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pinangat |
E338025
|
entity |
| Predicate | typicallyCookedIn |
P61222
|
FINISHED |
| Object | clay pot |
—
|
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: clay pot | Statement: [Pinangat, typicallyCookedIn, clay pot]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicallyCookedIn Context triple: [Pinangat, typicallyCookedIn, clay pot]
-
A.
isUsuallyCookedIn
chosen
Indicates that something is most commonly or typically prepared or cooked within a particular container, appliance, or environment.
-
B.
isCookedBy
Indicates that something has been prepared or made ready for eating through cooking by a particular agent.
-
C.
usesCookingMethod
Indicates that one entity prepares or processes another entity by applying a specific cooking technique or method.
-
D.
isEatenIn
Indicates that one entity (typically food) is consumed within the context, location, or occasion specified by another entity.
-
E.
eatenWithUtensil
Indicates that something was eaten using a specific utensil as the means of consumption.
- 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_69d81c664e48819088cbd8f433aeffe5 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de3c88b5e48190b0f0149102c08992 |
completed | April 14, 2026, 1:09 p.m. |
| PD | Predicate disambiguation | batch_69de05adef888190b023ab42ef5076b6 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:20 p.m.