Triple
T27866006
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monster Zero Ultra |
E704360
|
entity |
| Predicate | isConsumedFor |
P149984
|
FINISHED |
| Object | energy boost |
—
|
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: energy boost | Statement: [Monster Zero Ultra, isConsumedFor, energy boost]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isConsumedFor Context triple: [Monster Zero Ultra, isConsumedFor, energy boost]
-
A.
isConsumedIn
Indicates that one entity is used up, ingested, or otherwise expended as part of a process, event, or action involving another entity.
-
B.
consumedFor
chosen
Indicates that one entity is used up, spent, or depleted in order to produce, enable, or obtain another entity.
-
C.
isConsumedBy
Indicates that one entity is eaten, drunk, or otherwise ingested or used up by another entity.
-
D.
consumedAfter
Indicates that one item is consumed only after another specified item has been consumed.
-
E.
consumptionState
Indicates the current status or condition of how something is being used up, consumed, or depleted.
- 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_69ef840f12408190b539d00d79658abf |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f67257b0448190a13011af81c81449 |
completed | May 2, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69f66ec3d3d48190ab2f2b71939e572e |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 27, 2026, 6:21 p.m.