Triple
T2348380
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schaefer Brewing Company |
E45185
|
entity |
| Predicate | hasMarketingStrategy |
P13750
|
FINISHED |
| Object | sports event sponsorship |
—
|
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: sports event sponsorship | Statement: [Schaefer Brewing Company, hasMarketingStrategy, sports event sponsorship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMarketingStrategy Context triple: [Schaefer Brewing Company, hasMarketingStrategy, sports event sponsorship]
-
A.
hasMarketingCategory
Indicates that an entity is associated with a specific marketing category or segment used for classification or targeting.
-
B.
hasMarketingRole
Indicates that an entity holds a position or responsibility related to marketing activities within an organization.
-
C.
hasMarket
Indicates that an entity possesses, operates in, or is associated with a particular market or marketplace.
-
D.
marketingStrategy
chosen
Indicates the approach or plan an entity uses to promote, position, and sell its products or services to a target audience.
-
E.
marketStrategy
Indicates the approach or plan an entity uses to promote, position, and sell its products or services in a target market.
- 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.