Triple
T37662726
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Potion of Fire Resistance |
E937751
|
entity |
| Predicate | brewingBasePotion |
P188629
|
FINISHED |
| Object | Awkward Potion |
—
|
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: Awkward Potion | Statement: [Potion of Fire Resistance, brewingBasePotion, Awkward Potion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: brewingBasePotion Context triple: [Potion of Fire Resistance, brewingBasePotion, Awkward Potion]
-
A.
basePotion
chosen
Indicates that one entity serves as the foundational or primary potion from which another potion or effect is derived.
-
B.
givesPotionTo
Indicates that one entity provides or hands over a potion to another entity.
-
C.
brewingControl
Indicates that an entity manages, adjusts, or oversees the parameters and process of brewing another entity (such as a beverage or batch).
-
D.
brewingMethod
Indicates the technique or process used to brew or prepare a beverage, typically coffee or tea.
-
E.
brewedAccordingTo
Indicates that something has been produced or prepared following a specified brewing method, recipe, or standard.
- 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_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd166a488190b1bf9316b0790801 |
completed | May 6, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:18 p.m.