Triple
T37707366
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Potion of Poison |
E939230
|
entity |
| Predicate | canBeBrewed |
P200426
|
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, canBeBrewed, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeBrewed Context triple: [Potion of Poison, canBeBrewed, true]
-
A.
canBeBrewedIn
Indicates that a beverage or mixture is capable of being prepared or produced within a specified container, vessel, or brewing apparatus.
-
B.
cannotBeBrewedWith
Indicates that two items are incompatible such that they must not be combined together in the same brewing process.
-
C.
cannotBeBrewedWithout
Indicates that one entity is an essential ingredient or component for brewing another, such that the latter cannot be produced without the former.
-
D.
brewedUsing
Indicates that one entity was produced or prepared by using another entity as an ingredient, material, or component in a brewing process.
-
E.
brewedAccordingTo
Indicates that something has been produced or prepared following a specified brewing method, recipe, or standard.
- F. None of above. chosen
Provenance (4 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_69ff891e4b9c8190aa86a339a8944496 |
completed | May 9, 2026, 7:21 p.m. |
| PD | Predicate disambiguation | batch_69ff8801180c8190b23e20996ca68e0a |
completed | May 9, 2026, 7:16 p.m. |
| PDg | Predicate description generation | batch_69ff891d54248190be8742197564605a |
completed | May 9, 2026, 7:21 p.m. |
Created at: May 3, 2026, 4:18 p.m.