Triple
T37662534
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Potion of Weakness |
E937747
|
entity |
| Predicate | canCreateCloudAs |
P85293
|
FINISHED |
| Object | Lingering Potion of Weakness |
—
|
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: Lingering Potion of Weakness | Statement: [Potion of Weakness, canCreateCloudAs, Lingering Potion of Weakness]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canCreateCloudAs Context triple: [Potion of Weakness, canCreateCloudAs, Lingering Potion of Weakness]
-
A.
hasCloudComposition
Indicates that an atmospheric body or region possesses a specific composition or makeup of clouds.
-
B.
canDeployAs
chosen
Indicates that one entity is capable of being deployed or instantiated in the role, form, or environment represented by another entity.
-
C.
supportsCloudImages
Indicates that an entity is capable of handling, displaying, or otherwise working with images stored or managed in a cloud environment.
-
D.
usesCloudTechnologyFrom
Indicates that one entity employs or relies on cloud-based technology, services, or infrastructure provided by another entity.
-
E.
canDeploy
Indicates that one entity has the permission or capability to deploy another entity (such as software, resources, or configurations) into a target environment.
- 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_69f76ed6df7c8190b018e5baea716ceb |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbaa1321b48190af92a3e7ec24ec5b |
completed | May 6, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69fba8860f98819080b7bab05837b974 |
completed | May 6, 2026, 8:45 p.m. |
Created at: May 3, 2026, 4:18 p.m.