Triple
T5111215
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hogsmeade |
E115216
|
entity |
| Predicate | hasDrinkSpeciality |
P47505
|
FINISHED |
| Object | butterbeer |
—
|
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: butterbeer | Statement: [Hogsmeade, hasDrinkSpeciality, butterbeer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDrinkSpeciality Context triple: [Hogsmeade, hasDrinkSpeciality, butterbeer]
-
A.
hasDrinkNamedAfter
Indicates that one entity has a beverage that is named after another entity.
-
B.
traditionalDrink
Indicates that one entity is a beverage customarily consumed within the culture, heritage, or longstanding practices associated with another entity.
-
C.
hasFlagshipBeerCharacteristics
Indicates that one beer possesses the defining qualities or signature traits typically associated with a brewery’s primary or flagship beer.
-
D.
signatureDrink
chosen
Indicates that a particular drink is the characteristic or specially associated beverage of an entity (such as a person, venue, or brand).
-
E.
drinks
Indicates that one entity consumes a liquid substance, typically by ingesting it through the mouth.
- 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_69bd4441d1648190a54a533895041987 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd75ad362c8190b9cbded390aaea3c |
completed | March 20, 2026, 4:28 p.m. |
| PD | Predicate disambiguation | batch_69bd715fe3a8819087d3065adddba515 |
completed | March 20, 2026, 4:10 p.m. |
Created at: March 20, 2026, 1:41 p.m.