Triple
T184432
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heineken Experience brewery |
E3949
|
entity |
| Predicate | rebrandedAsHeinekenExperience |
P6656
|
FINISHED |
| Object | 2008 |
—
|
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: 2008 | Statement: [Heineken Experience brewery, rebrandedAsHeinekenExperience, 2008]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rebrandedAsHeinekenExperience Context triple: [Heineken Experience brewery, rebrandedAsHeinekenExperience, 2008]
-
A.
formerBrand
Indicates that an entity was previously used or recognized as a brand for another entity but is no longer its current brand.
-
B.
hasChampagneBar
Indicates that an entity includes, features, or is equipped with a champagne bar.
-
C.
replacedVenue
Indicates that one venue has taken the place of another as its successor location or site.
-
D.
introducedTo
Indicates that one entity caused or facilitated a first meeting or formal presentation between another entity and a third party.
-
E.
brand
Indicates that one entity is the commercial brand or label under which another entity (such as a product, service, or organization) is marketed or identified.
- F. None of above. chosen
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_69a25497e2f08190a040f8c6e1842643 |
completed | Feb. 28, 2026, 2:36 a.m. |
| NER | Named-entity recognition | batch_69a25926be9c8190a4cfce66f57589d1 |
completed | Feb. 28, 2026, 2:55 a.m. |
| PD | Predicate disambiguation | batch_69a2566fb08c81908faff2fde552105d |
completed | Feb. 28, 2026, 2:43 a.m. |
| PDg | Predicate description generation | batch_69a257e763d081908c54ad57d8d3060d |
completed | Feb. 28, 2026, 2:50 a.m. |
Created at: Feb. 28, 2026, 2:40 a.m.