Triple
T27914455
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Teochew oyster omelette |
E706029
|
entity |
| Predicate | servedWithUtensil |
P26230
|
FINISHED |
| Object | chopsticks |
—
|
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: chopsticks | Statement: [Teochew oyster omelette, servedWithUtensil, chopsticks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servedWithUtensil Context triple: [Teochew oyster omelette, servedWithUtensil, chopsticks]
-
A.
eatenWithUtensil
chosen
Indicates that something was eaten using a specific utensil as the means of consumption.
-
B.
worksInKitchenAt
Indicates that an entity performs work or duties in the kitchen area of a specified location or organization.
-
C.
isUsuallyCookedIn
Indicates that something is most commonly or typically prepared or cooked within a particular container, appliance, or environment.
-
D.
usesCookingMethod
Indicates that one entity prepares or processes another entity by applying a specific cooking technique or method.
-
E.
usesIngredient
Indicates that one entity employs or incorporates another entity as an ingredient in its composition or creation.
- 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_69ef96b6cc808190aab19fb18b235f4b |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69fd35d108908190b79b1e8e6bbd62aa |
completed | May 8, 2026, 1:01 a.m. |
| PD | Predicate disambiguation | batch_69fd34cb46108190b43c3b7f67ec4cd4 |
completed | May 8, 2026, 12:56 a.m. |
Created at: April 27, 2026, 6:52 p.m.