Triple
T32068009
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monsters, Inc. scare floor |
E818935
|
entity |
| Predicate | energyStoredIn |
P4607
|
FINISHED |
| Object | scream canisters |
—
|
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: scream canisters | Statement: [Monsters, Inc. scare floor, energyStoredIn, scream canisters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: energyStoredIn Context triple: [Monsters, Inc. scare floor, energyStoredIn, scream canisters]
-
A.
storesEnergyAs
chosen
Indicates that one entity retains or accumulates energy in the form or medium specified by another entity.
-
B.
energyPotential
Indicates a relationship where one entity possesses or confers the capacity to perform work or cause change (potential energy) relative to another entity or state.
-
C.
energyContribution
Indicates the amount or role of energy that one entity provides or contributes to another entity, process, or system.
-
D.
usesEnergyFrom
Indicates that one entity derives or consumes energy originating from another entity as its source.
-
E.
outputEnergy
Indicates that an entity produces or releases a certain amount or form of energy as a result of its operation or behavior.
- 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_69f348fecc088190af1470afe5a969f0 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6f8164698819090c1b471f1caa4c6 |
completed | May 3, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69f6f6619404819084662aef1238261c |
completed | May 3, 2026, 7:16 a.m. |
Created at: May 1, 2026, 12:22 a.m.