Triple
T38048555
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Empire Brewery |
E949688
|
entity |
| Predicate | notableBrewer |
P139843
|
FINISHED |
| Object | Jacob Best |
E281135
|
NE 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: Jacob Best | Statement: [Empire Brewery, notableBrewer, Jacob Best]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableBrewer Context triple: [Empire Brewery, notableBrewer, Jacob Best]
-
A.
notableBrewmaster
Indicates that an entity is recognized for being an outstanding or distinguished brewmaster, typically noted for significant skill, influence, or achievement in brewing.
-
B.
knownBrewer
chosen
Indicates that one entity is recognized as the brewer (producer of beer or similar beverages) associated with another entity.
-
C.
notableWinemaker
Indicates that the subject is recognized as a distinguished or prominent winemaker.
-
D.
notableDrinker
Indicates that the subject is known or recognized for their drinking behavior, typically due to frequency, quantity, or notoriety.
-
E.
hasNotableBeer
Indicates that an entity is associated with a beer that is recognized as distinctive, famous, or otherwise noteworthy.
- F. None of above.
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_69f76f000cf081908c11fb5443b392e6 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037df1223c8190a5d61e4f8e6fd613 |
completed | May 12, 2026, 7:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a4171134a148190987567d487560f2e |
completed | June 28, 2026, 7:08 p.m. |
| PD | Predicate disambiguation | batch_6a037a1ad6c48190bfe35d350c1b4751 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:20 p.m.