Triple
T25181624
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Truman Brewery |
E630598
|
entity |
| Predicate | ceasedBrewingOnSite |
P99434
|
FINISHED |
| Object | late 20th century |
—
|
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: late 20th century | Statement: [Truman Brewery, ceasedBrewingOnSite, late 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ceasedBrewingOnSite Context triple: [Truman Brewery, ceasedBrewingOnSite, late 20th century]
-
A.
hasBreweryOrFacility
Indicates that an entity possesses, operates, or is associated with a brewery or brewing-related facility.
-
B.
ceasedManufacturingIn
chosen
Indicates that an entity stopped producing or manufacturing a product, item, or category in a specified location or at a specified time.
-
C.
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.
-
D.
hasMajorBrewery
Indicates that a location or entity possesses or hosts a large, commercially significant brewery.
-
E.
brewedAt
Indicates that a beverage or batch was produced or brewed at a specific location or facility.
- 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_69e75a88fdf081908e47ae6e195c14e1 |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f46dc784448190ba2ef45b1d688ec9 |
completed | May 1, 2026, 9:09 a.m. |
| PD | Predicate disambiguation | batch_69f44d8043b081908bbffd7f044b4f26 |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 21, 2026, 12:36 p.m.