Triple
T37662639
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Potion of Healing |
E937749
|
entity |
| Predicate | canBeBrewedIn |
P199867
|
FINISHED |
| Object | brewing stand |
—
|
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: brewing stand | Statement: [Potion of Healing, canBeBrewedIn, brewing stand]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeBrewedIn Context triple: [Potion of Healing, canBeBrewedIn, brewing stand]
-
A.
brewedUsing
Indicates that one entity was produced or prepared by using another entity as an ingredient, material, or component in a brewing process.
-
B.
cannotBeBrewedWith
Indicates that two items are incompatible such that they must not be combined together in the same brewing process.
-
C.
brewedAccordingTo
Indicates that something has been produced or prepared following a specified brewing method, recipe, or standard.
-
D.
cannotBeBrewedWithout
Indicates that one entity is an essential ingredient or component for brewing another, such that the latter cannot be produced without the former.
-
E.
teaType
Indicates the specific variety or category of tea associated with an entity.
- 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_69f76ed6df7c8190b018e5baea716ceb |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff5f5ecc808190b2df364da108ff4c |
completed | May 9, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69ff5b84131c8190bf81d7fb53e934bc |
completed | May 9, 2026, 4:06 p.m. |
| PDg | Predicate description generation | batch_69ff5f5ddfcc819092563419f9e82d60 |
completed | May 9, 2026, 4:22 p.m. |
Created at: May 3, 2026, 4:18 p.m.