Triple
T37662733
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Potion of Fire Resistance |
E937751
|
entity |
| Predicate | hasLingeringVariant |
P189177
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Potion of Fire Resistance, hasLingeringVariant, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLingeringVariant Context triple: [Potion of Fire Resistance, hasLingeringVariant, true]
-
A.
hasVariant
Indicates that one entity exists as an alternative form, version, or variation of another entity.
-
B.
hasVariantsIn
Indicates that an entity exists in multiple alternative forms or versions within a specified context or set.
-
C.
hasTemporalVariant
Indicates that one entity is a version or form of another that exists or applies at a different time or temporal context.
-
D.
lingeringVariantEffect
chosen
Indicates that the effects of a particular variant persist over time, continuing to influence the related entity or process beyond the initial event.
-
E.
hasMutableVariant
Indicates that an entity has a related version or form that can be changed or modified (i.e., a mutable counterpart).
- 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_69ff1a972bf08190860696ffcd887c0f |
completed | May 9, 2026, 11:29 a.m. |
| PD | Predicate disambiguation | batch_69ff184005d88190bf38283ebc499b28 |
completed | May 9, 2026, 11:19 a.m. |
Created at: May 3, 2026, 4:18 p.m.