Triple
T11794559
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shulker |
E280471
|
entity |
| Predicate | inflictsEffect |
P100772
|
FINISHED |
| Object | Levitation |
—
|
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: Levitation | Statement: [Shulker, inflictsEffect, Levitation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inflictsEffect Context triple: [Shulker, inflictsEffect, Levitation]
-
A.
attackEffect
chosen
Indicates that one entity’s attack produces a specific effect or consequence on another entity.
-
B.
damageEffect
Indicates that one entity causes harm, reduction, or deterioration to another entity or its properties.
-
C.
involvedPhysicalEffect
Indicates that one entity participates in causing, experiencing, or mediating a physical effect on another entity or the environment.
-
D.
ultimateEffect
Indicates the final or overall outcome that results from a preceding action, condition, or sequence of events.
-
E.
effectOfDeath
Indicates the causal impact or consequences that a death has on another entity, state, or process.
- 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_69d6ab258b808190b1735835c841e3a4 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a5a082d08190a42541396a06ed98 |
completed | April 10, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69d8a2491f048190853239bc05090bf4 |
completed | April 10, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:42 p.m.