Triple
T37662533
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Potion of Weakness |
E937747
|
entity |
| Predicate | canBeThrownAs |
P118561
|
FINISHED |
| Object | Splash 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: Splash Potion of Weakness | Statement: [Potion of Weakness, canBeThrownAs, Splash Potion of Weakness]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeThrownAs Context triple: [Potion of Weakness, canBeThrownAs, Splash Potion of Weakness]
-
A.
canBeThrown
chosen
Indicates that an entity is suitable or able to be propelled through the air by being thrown.
-
B.
canBeThrownBy
Indicates that one entity is capable of being thrown or launched by another entity.
-
C.
canBeCaughtAs
Indicates that one entity is capable of being captured, intercepted, or seized by another entity under certain conditions.
-
D.
canBeCaughtWith
Indicates that one entity is capable of being captured, obtained, or discovered using another specified entity or method.
-
E.
canBeCaught
Indicates that one entity is capable of being captured, seized, or apprehended by another entity.
- 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_69ff5803c02c81908b63067119f5e684 |
completed | May 9, 2026, 3:51 p.m. |
| PD | Predicate disambiguation | batch_69ff576d8b308190b49a1e072a0ae661 |
completed | May 9, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:18 p.m.