Triple
T33968211
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | August A. Busch Jr. |
E870915
|
entity |
| Predicate | notableEmployerBrand |
P20563
|
FINISHED |
| Object | Budweiser |
E701904
|
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: Budweiser | Statement: [August A. Busch Jr., notableEmployerBrand, Budweiser]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableEmployerBrand Context triple: [August A. Busch Jr., notableEmployerBrand, Budweiser]
-
A.
notableEmployerFeature
Indicates that an employer is distinguished or recognized for a particular characteristic, quality, or attribute.
-
B.
notableEmployer
chosen
Indicates that an entity has been employed by, or has worked for, a particularly significant or noteworthy organization or individual.
-
C.
typicalEmployerBrand
Indicates that an entity is the employer brand that is most commonly or characteristically associated with another entity.
-
D.
employerBrandingFor
Indicates that one entity develops, manages, or represents the employer brand or employer reputation on behalf of another entity.
-
E.
notableEnterprise
Indicates that an entity is a business or commercial organization recognized for its significance, prominence, or impact.
- 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_69f3499ce8e88190b66e1d49ad8c7037 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3692d678308190a75199a0ba6ee639 |
completed | June 20, 2026, 1:17 p.m. |
| PD | Predicate disambiguation | batch_6a0379f963908190846d232f386fd98f |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:50 a.m.