Triple
T2348397
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schaefer Brewing Company |
E45185
|
entity |
| Predicate | hasAdvertisingMedium |
P7961
|
FINISHED |
| Object | billboards |
—
|
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: billboards | Statement: [Schaefer Brewing Company, hasAdvertisingMedium, billboards]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAdvertisingMedium Context triple: [Schaefer Brewing Company, hasAdvertisingMedium, billboards]
-
A.
hasMediaOutlet
Indicates that one entity possesses, controls, or is associated with a media outlet (such as a newspaper, TV channel, or online news platform).
-
B.
hasAssociatedMedium
chosen
Indicates that one entity is linked to another entity that serves as its medium, format, or channel of expression or transmission.
-
C.
hasMarketingCategory
Indicates that an entity is associated with a specific marketing category or segment used for classification or targeting.
-
D.
hasCommonMedia
Indicates that two entities share at least one media item (such as an image, video, or audio file) in common.
-
E.
eligibleMedia
Indicates that certain media items qualify under specified conditions or rules for participation, use, or consideration in a given context.
- 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.