Triple
T27956169
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Victoria |
E703555
|
entity |
| Predicate | globalBrandPortfolio |
P99659
|
FINISHED |
| Object | AB InBev global brands |
—
|
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: AB InBev global brands | Statement: [Victoria, globalBrandPortfolio, AB InBev global brands]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: globalBrandPortfolio Context triple: [Victoria, globalBrandPortfolio, AB InBev global brands]
-
A.
partOfBrandPortfolioOf
chosen
Indicates that one brand is included within, and belongs to, the overall brand portfolio of another entity.
-
B.
hasBrandRecognitionFor
Indicates that one entity is aware of, recognizes, or can identify the brand of another entity.
-
C.
associatedBrandCollection
Indicates a relationship where one or more brands are grouped or linked together as part of a specific collection.
-
D.
parentBrand
Indicates that one brand is the overarching or owning brand from which another brand is derived or subordinated.
-
E.
hasGlobalBrand
Indicates that an entity possesses a brand that is recognized and operates across multiple countries or worldwide.
- 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_69ef840c8b2c8190946ae9522774ba51 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f63b317e048190963989b732b25b91 |
completed | May 2, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69f6370ea79c81909b761821ee0fa698 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 7:28 p.m.