Triple
T20878531
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fizzy Lifting Drinks |
E514083
|
entity |
| Predicate | requiresActionToCounteract |
P48723
|
FINISHED |
| Object | burping |
—
|
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: burping | Statement: [Fizzy Lifting Drinks, requiresActionToCounteract, burping]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresActionToCounteract Context triple: [Fizzy Lifting Drinks, requiresActionToCounteract, burping]
-
A.
requiredAction
chosen
Indicates that a specific action must be performed or fulfilled as a necessary condition in the given context.
-
B.
requiresActionFrom
Indicates that one entity is obligated to perform or initiate some action in response to or as a consequence of another entity or situation.
-
C.
forcedActionDescribedIn
Indicates that an action was carried out under compulsion or coercion as described in a particular source or description.
-
D.
requiresApplicationOf
Indicates that performing one entity or process depends on actively applying or using another entity, method, or resource.
-
E.
requires
Indicates that one entity must exist, occur, or be satisfied before another entity can exist, occur, or be carried out.
- 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_69e0b4f733f081908a401c0b7beb0b9f |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c6775f108190a79cd5e8c31cecf6 |
completed | April 21, 2026, 12:36 a.m. |
| PD | Predicate disambiguation | batch_69e5c9a8dc148190b33ff51894e2a8f9 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:45 p.m.