Triple
T4940934
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Burton upon Trent |
E110929
|
entity |
| Predicate | brewingTechniqueInfluence |
P60157
|
FINISHED |
| Object | Burtonisation |
—
|
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: Burtonisation | Statement: [Burton upon Trent, brewingTechniqueInfluence, Burtonisation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: brewingTechniqueInfluence Context triple: [Burton upon Trent, brewingTechniqueInfluence, Burtonisation]
-
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.
brewingTemperature
Indicates the specific temperature at which a brewing process is carried out.
-
D.
notableBrewmaster
Indicates that an entity is recognized for being an outstanding or distinguished brewmaster, typically noted for significant skill, influence, or achievement in brewing.
-
E.
fermentationMethod
Indicates the process or technique by which a substance is fermented to achieve a desired transformation or product.
- 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_69bd4415eee08190bdce70276e56a5b4 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd708ba9888190baf4e79c8f159e9f |
completed | March 20, 2026, 4:06 p.m. |
| PD | Predicate disambiguation | batch_69bd6c389b9881908ad7fb1c5393c1b1 |
completed | March 20, 2026, 3:48 p.m. |
| PDg | Predicate description generation | batch_69bd6ff85b50819081d78087caa6b473 |
completed | March 20, 2026, 4:04 p.m. |
Created at: March 20, 2026, 1:31 p.m.