Triple
T2348386
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schaefer Brewing Company |
E45185
|
entity |
| Predicate | mainProductType |
P7216
|
FINISHED |
| Object | beer |
—
|
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: beer | Statement: [Schaefer Brewing Company, mainProductType, beer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainProductType Context triple: [Schaefer Brewing Company, mainProductType, beer]
-
A.
primaryProduct
chosen
Indicates that one entity is the main or most important product associated with, produced by, or offered by another entity.
-
B.
productFamily
Indicates that one product belongs to, or is categorized under, a broader product family or line.
-
C.
notableProductType
Indicates that an entity is particularly well-known or distinguished for producing or offering a specific type of product.
-
D.
primaryDeviceCategory
Indicates the main type or class of device associated with an entity or event, distinguishing it from other possible device categories.
-
E.
productTypeEvaluated
Indicates that an entity’s product type has been assessed or judged according to certain criteria or standards.
- 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_69a88917935081909b755dbf38e81024 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abcade3c808190ab3803538ccbe620 |
completed | March 7, 2026, 6:51 a.m. |
| PD | Predicate disambiguation | batch_69abc59616a8819099711834e6f1ccd6 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:52 p.m.