Triple
T32773193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bilimoria |
E838118
|
entity |
| Predicate | hasNotableBrandAssociated |
P96602
|
FINISHED |
| Object | Cobra Beer |
—
|
NE NERFINISHED |
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: Cobra Beer | Statement: [Bilimoria, hasNotableBrandAssociated, Cobra Beer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableBrandAssociated Context triple: [Bilimoria, hasNotableBrandAssociated, Cobra Beer]
-
A.
hasNotableBrandAssociation
chosen
Indicates that there is a significant, recognizable, or influential brand linked or connected to the subject entity.
-
B.
hasNotableSubBrand
Indicates that an entity includes or owns a distinct, well-known sub-brand associated with it.
-
C.
hasBrandRole
Indicates that an entity holds a specific functional or organizational role in relation to a particular brand.
-
D.
hasNotableCompany
Indicates that an entity is associated with or linked to a company that is considered notable or significant in some context.
-
E.
hasCoBrand
Indicates that two brands are jointly associated or partnered in offering a product, service, or marketing initiative.
- 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_69f3493a824c8190938489ba69041d08 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a0144c75aec81908bdd9e88f2af737a |
completed | May 11, 2026, 2:53 a.m. |
| PD | Predicate disambiguation | batch_6a014405a2d48190a1d58b0b907ad696 |
completed | May 11, 2026, 2:50 a.m. |
Created at: May 1, 2026, 1:13 a.m.