Triple
T37707369
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Potion of Poison |
E939230
|
entity |
| Predicate | requiresBrewingStand |
P188630
|
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 Poison, requiresBrewingStand, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresBrewingStand Context triple: [Potion of Poison, requiresBrewingStand, true]
-
A.
brewingStandRequired
chosen
Indicates that the action or process requires the presence or use of a brewing stand to occur.
-
B.
canBeBrewedIn
Indicates that a beverage or mixture is capable of being prepared or produced within a specified container, vessel, or brewing apparatus.
-
C.
canBeBrewed
Indicates that something is suitable or able to be prepared by brewing.
-
D.
requiresBrewingKnowledgeOf
Indicates that performing or understanding the subject action or entity depends on having knowledge or expertise in brewing.
-
E.
cannotBeBrewedWithout
Indicates that one entity is an essential ingredient or component for brewing another, such that the latter cannot be produced without the former.
- 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_69f76edb49dc8190b951dce9ce6ef789 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a00a094c44c81908e4501151688a635 |
completed | May 10, 2026, 3:13 p.m. |
| PD | Predicate disambiguation | batch_6a009fcdfd848190841deaad9667d347 |
completed | May 10, 2026, 3:10 p.m. |
Created at: May 3, 2026, 4:18 p.m.