Triple
T22852913
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 삼계탕 |
E566398
|
entity |
| Predicate | consumedFor |
P149984
|
FINISHED |
| Object | health benefits |
—
|
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: health benefits | Statement: [삼계탕, consumedFor, health benefits]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: consumedFor Context triple: [삼계탕, consumedFor, health benefits]
-
A.
consumedAfter
Indicates that one item is consumed only after another specified item has been consumed.
-
B.
isConsumedIn
Indicates that one entity is used up, ingested, or otherwise expended as part of a process, event, or action involving another entity.
-
C.
consumes
Indicates that one entity eats, drinks, or otherwise uses up another entity as a resource or nourishment.
-
D.
isConsumedBy
Indicates that one entity is eaten, drunk, or otherwise ingested or used up by another entity.
-
E.
consumptionState
Indicates the current status or condition of how something is being used up, consumed, or depleted.
- F. None of above. chosen
Provenance (4 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_69e2458750b481908a8e4cf4609cc6cf |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17eba65a881908c484262c3ee5212 |
completed | April 29, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69eed2d507c08190895ed971af0fc755 |
completed | April 27, 2026, 3:07 a.m. |
| PDg | Predicate description generation | batch_69eeeb577e2081909f4a4e9c296535c0 |
completed | April 27, 2026, 4:51 a.m. |
Created at: April 17, 2026, 3:36 p.m.