Triple
T28947184
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arthur Guinness & Son |
E730610
|
entity |
| Predicate | operatedBrewery |
P77072
|
FINISHED |
| Object | St. James's Gate Brewery |
—
|
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: St. James's Gate Brewery | Statement: [Arthur Guinness & Son, operatedBrewery, St. James's Gate Brewery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatedBrewery Context triple: [Arthur Guinness & Son, operatedBrewery, St. James's Gate Brewery]
-
A.
numberOfBreweries
Indicates the count of breweries associated with a given entity or within a specified context.
-
B.
knownBrewer
Indicates that one entity is recognized as the brewer (producer of beer or similar beverages) associated with another entity.
-
C.
hasBreweryOrFacility
chosen
Indicates that an entity possesses, operates, or is associated with a brewery or brewing-related facility.
-
D.
breweryType
Indicates the specific category or classification of a brewery based on its operational or business characteristics.
-
E.
hasBreweryFocus
Indicates that an entity (such as a business, product, or activity) is primarily oriented around, specialized in, or dedicated to breweries or brewing-related operations.
- 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_69f043ea0aa88190a25acbf46157995a |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69fed48d8e148190a99c0aea29f8a3ee |
completed | May 9, 2026, 6:30 a.m. |
| PD | Predicate disambiguation | batch_69fed3c82a24819095e614e31ac0307f |
completed | May 9, 2026, 6:27 a.m. |
Created at: April 28, 2026, 8:41 a.m.