Triple
T26404241
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sapporo Beer Museum |
E663786
|
entity |
| Predicate | hasTypeOfBeerServed |
P125041
|
FINISHED |
| Object | Sapporo Draft Beer |
—
|
NE NERFINISHED |
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: Sapporo Draft Beer | Statement: [Sapporo Beer Museum, hasTypeOfBeerServed, Sapporo Draft Beer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfBeerServed Context triple: [Sapporo Beer Museum, hasTypeOfBeerServed, Sapporo Draft Beer]
-
A.
hasFlagshipBeerCharacteristics
Indicates that one beer possesses the defining qualities or signature traits typically associated with a brewery’s primary or flagship beer.
-
B.
servedDrink
Indicates that one entity provided or presented a drink to another entity.
-
C.
isSessionBeer
Indicates that a beer is classified as a “session beer,” meaning it has relatively low alcohol content and is suitable for extended, casual drinking sessions.
-
D.
hasNotableBeer
chosen
Indicates that an entity is associated with a beer that is recognized as distinctive, famous, or otherwise noteworthy.
-
E.
isMixedBeer
Indicates that a beer is composed by mixing two or more different beers together.
- 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_69ee883931888190901be96d75ee23cc |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f7308a096081909d66a56f3c926806 |
completed | May 3, 2026, 11:24 a.m. |
| PD | Predicate disambiguation | batch_69f72a00c5f081908b6539d15baf4e12 |
completed | May 3, 2026, 10:57 a.m. |
Created at: April 26, 2026, 11:33 p.m.