Triple
T26140920
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fire Mario |
E659513
|
entity |
| Predicate | fireballBehavior |
P159989
|
FINISHED |
| Object | bounces along the ground |
—
|
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: bounces along the ground | Statement: [Fire Mario, fireballBehavior, bounces along the ground]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fireballBehavior Context triple: [Fire Mario, fireballBehavior, bounces along the ground]
-
A.
fireballExplosionPower
Indicates the magnitude or intensity of an explosion produced by a fireball.
-
B.
fireEffect
Indicates that one entity produces, causes, or is associated with a fire-related impact or consequence on another entity.
-
C.
fireballFrequency
Indicates how often fireball events occur or are produced within a given context or time period.
-
D.
fireballDiameter
Indicates the measured or specified width of a fireball across its widest point.
-
E.
fireUse
Indicates the use or application of fire by one entity on, with, or for another entity or object.
- 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_69ee5bc496a88190af7deb7ab5e081de |
completed | April 26, 2026, 6:39 p.m. |
| NER | Named-entity recognition | batch_69f60be435b48190a389ebb5a4537a16 |
completed | May 2, 2026, 2:36 p.m. |
| PD | Predicate disambiguation | batch_69f5b0021da88190bdd4cf2698c23edf |
completed | May 2, 2026, 8:04 a.m. |
| PDg | Predicate description generation | batch_69f5f6b32a8881909baa0db57b80d56a |
completed | May 2, 2026, 1:05 p.m. |
Created at: April 26, 2026, 8:20 p.m.