Triple
T37668697
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Icehouse |
E937889
|
entity |
| Predicate | brewingProcessDetail |
P60157
|
FINISHED |
| Object | beer partially frozen and ice crystals removed |
—
|
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: beer partially frozen and ice crystals removed | Statement: [Icehouse, brewingProcessDetail, beer partially frozen and ice crystals removed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: brewingProcessDetail Context triple: [Icehouse, brewingProcessDetail, beer partially frozen and ice crystals removed]
-
A.
brewingMethod
Indicates the technique or process used to brew or prepare a beverage, typically coffee or tea.
-
B.
brewingTime
Indicates the duration required to brew or prepare a beverage or similar concoction.
-
C.
brewingControl
Indicates that an entity manages, adjusts, or oversees the parameters and process of brewing another entity (such as a beverage or batch).
-
D.
brewedAccordingTo
Indicates that something has been produced or prepared following a specified brewing method, recipe, or standard.
-
E.
brewingTechniqueInfluence
chosen
Indicates how a particular brewing technique affects or modifies the characteristics or outcome of a brewing process.
- 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_69f76ed6df7c8190b018e5baea716ceb |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbc9d1dba881908c399b8e1dc13ce2 |
completed | May 6, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ec03ac8190a757563f96fab283 |
completed | May 6, 2026, 11:04 p.m. |
Created at: May 3, 2026, 4:18 p.m.