Triple
T20473088
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pepper Imps |
E502241
|
entity |
| Predicate | hasConsumerReaction |
P97670
|
FINISHED |
| Object | surprise at breathing fire |
—
|
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: surprise at breathing fire | Statement: [Pepper Imps, hasConsumerReaction, surprise at breathing fire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasConsumerReaction Context triple: [Pepper Imps, hasConsumerReaction, surprise at breathing fire]
-
A.
isAReactionTo
Indicates that one event, action, or state occurs as a direct response or consequence of another.
-
B.
causedReaction
chosen
Indicates that one entity’s action or state brought about a specific reaction or response in another entity.
-
C.
receivedReaction
Indicates that an entity has been the target of a reaction or response from another entity.
-
D.
containsReaction
Indicates that one entity includes or encompasses a specific reaction as part of its contents or structure.
-
E.
hasUserAttitude
Indicates that one entity holds a particular attitude, opinion, or evaluative stance toward another entity or subject.
- 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_69e0b4ae5f1081908768b0c9a3a0bf38 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e69962d810819091bb13fe73250e24 |
completed | April 20, 2026, 9:23 p.m. |
| PD | Predicate disambiguation | batch_69e57679eb40819086142df3e39c928e |
completed | April 20, 2026, 12:42 a.m. |
Created at: April 16, 2026, 11:33 a.m.