Triple
T37662537
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Potion of Weakness |
E937747
|
entity |
| Predicate | brewingIngredient |
P162782
|
FINISHED |
| Object | fermented spider eye |
—
|
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: fermented spider eye | Statement: [Potion of Weakness, brewingIngredient, fermented spider eye]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: brewingIngredient Context triple: [Potion of Weakness, brewingIngredient, fermented spider eye]
-
A.
typeOfMalt
Indicates the specific kind or category of malt used or referenced in relation to another entity.
-
B.
hasMashBill
Indicates that an alcoholic beverage (typically a spirit like whiskey or bourbon) is produced using a specific mixture of grains (the mash bill).
-
C.
brewedUsing
chosen
Indicates that one entity was produced or prepared by using another entity as an ingredient, material, or component in a brewing process.
-
D.
brewable
Indicates that something can be prepared or produced by brewing, typically through steeping or boiling in liquid.
-
E.
ingredientType
Indicates that one entity is classified as a specific type or category of ingredient in relation to another.
- 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_69fbb084760c8190a1554985d3c3cb7a |
completed | May 6, 2026, 9:20 p.m. |
| PD | Predicate disambiguation | batch_69fbadf3cb548190ba3b7514f76b790a |
completed | May 6, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:18 p.m.