Triple
T37769100
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Potion of Regeneration |
E941491
|
entity |
| Predicate | upgradedVariant |
P47073
|
FINISHED |
| Object | Potion of Regeneration II |
—
|
NE NERFINISHED |
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: Potion of Regeneration II | Statement: [Potion of Regeneration, upgradedVariant, Potion of Regeneration II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: upgradedVariant Context triple: [Potion of Regeneration, upgradedVariant, Potion of Regeneration II]
-
A.
upgradedBy
Indicates that an entity has been improved, enhanced, or moved to a higher version or level as a result of actions performed by another entity.
-
B.
upgradeOf
chosen
Indicates that one entity is a newer, improved, or more advanced version of another entity.
-
C.
wasUpgradedFor
Indicates that one entity was improved, enhanced, or updated specifically to serve, benefit, or be compatible with another entity.
-
D.
upgradeable
Indicates that an entity can be improved or enhanced to a higher version, level, or capability.
-
E.
upgradeFor
Indicates that one entity serves as an improved or enhanced replacement for 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_69f76ee3251881909bb4451aad50752b |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbc995dc2481908b3bd4217f8101e7 |
completed | May 6, 2026, 11:07 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ee04f08190977b7ad70fc85896 |
completed | May 6, 2026, 11:04 p.m. |
Created at: May 3, 2026, 4:19 p.m.