Triple
T29463696
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Telekinesis |
E747313
|
entity |
| Predicate | typicalAbilitiesInclude |
P39122
|
FINISHED |
| Object | levitation of objects |
—
|
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 of objects | Statement: [Telekinesis, typicalAbilitiesInclude, levitation of objects]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalAbilitiesInclude Context triple: [Telekinesis, typicalAbilitiesInclude, levitation of objects]
-
A.
typicalFeatures
Indicates that the related entities are characteristic or commonly occurring features or attributes of something.
-
B.
believedToHaveAbility
Indicates that one entity is thought or assumed to possess a particular capability or power, without asserting that the ability is actually verified.
-
C.
isCapableOf
chosen
Indicates that an entity has the ability or capacity to perform a particular action or function.
-
D.
typicalRequirement
Indicates that one entity is a standard or commonly expected prerequisite, condition, or necessity for another entity.
-
E.
capabilityType
Indicates the type or category of capability that an entity possesses or is associated with.
- 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_69f0bd4125f88190b56104591351619c |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_6a01c5c5dbb881909b19ba87a7760ee7 |
completed | May 11, 2026, 12:04 p.m. |
| PD | Predicate disambiguation | batch_6a01c549af98819098e0effd775b7710 |
completed | May 11, 2026, 12:02 p.m. |
Created at: April 28, 2026, 3:51 p.m.