Triple
T20361643
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wolfsbane Potion |
E496793
|
entity |
| Predicate | requiresBrewingKnowledgeOf |
P139844
|
FINISHED |
| Object | advanced potion theory |
—
|
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: advanced potion theory | Statement: [Wolfsbane Potion, requiresBrewingKnowledgeOf, advanced potion theory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresBrewingKnowledgeOf Context triple: [Wolfsbane Potion, requiresBrewingKnowledgeOf, advanced potion theory]
-
A.
brewedAccordingTo
Indicates that something has been produced or prepared following a specified brewing method, recipe, or standard.
-
B.
brewingMethod
Indicates the technique or process used to brew or prepare a beverage, typically coffee or tea.
-
C.
allowsTastingOf
Indicates that one entity permits another entity to sample or try the taste of something.
-
D.
hasCaffeineContent
Indicates that one entity (typically a beverage or substance) possesses a specified amount or presence of caffeine.
-
E.
notableBrewmaster
Indicates that an entity is recognized for being an outstanding or distinguished brewmaster, typically noted for significant skill, influence, or achievement in brewing.
- 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_69e0b4a3f7f48190b37f354574028ca6 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6786de5988190827584358c9db147 |
completed | April 20, 2026, 7:03 p.m. |
| PD | Predicate disambiguation | batch_69e57648be3c81908256838228cabf5c |
completed | April 20, 2026, 12:41 a.m. |
| PDg | Predicate description generation | batch_69e58d7481508190a87c8b88f9df9879 |
completed | April 20, 2026, 2:20 a.m. |
Created at: April 16, 2026, 11:25 a.m.