Triple
T34223850
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St James's Gate |
E877993
|
entity |
| Predicate | breweryCapacity |
P178548
|
FINISHED |
| Object | one of the largest stout breweries in the world |
—
|
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: one of the largest stout breweries in the world | Statement: [St James's Gate, breweryCapacity, one of the largest stout breweries in the world]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: breweryCapacity Context triple: [St James's Gate, breweryCapacity, one of the largest stout breweries in the world]
-
A.
breweryType
Indicates the specific category or classification of a brewery based on its operational or business characteristics.
-
B.
numberOfBreweries
Indicates the count of breweries associated with a given entity or within a specified context.
-
C.
numberOfBarrels
Indicates the quantity or count of barrels associated with a given entity or context.
-
D.
breweryLocation
Indicates the place where a brewery is situated or operates.
-
E.
breweryRelation
Indicates a relationship in which one entity is a brewery associated with, producing for, or otherwise linked to another entity (such as a brand, product, or location).
- 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_69f349b16d0481908754e3069f05e0c1 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f710aaff588190adc6cc5b7d5424cc |
completed | May 3, 2026, 9:08 a.m. |
| PD | Predicate disambiguation | batch_69f70f3c5bfc81908585f52e196dafe5 |
completed | May 3, 2026, 9:02 a.m. |
| PDg | Predicate description generation | batch_69f70fddd43c819088dee5a448c72cbe |
completed | May 3, 2026, 9:05 a.m. |
Created at: May 1, 2026, 1:55 a.m.