Triple
T184458
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heineken Experience brewery |
E3949
|
entity |
| Predicate | sells |
P1743
|
FINISHED |
| Object | Heineken-branded merchandise |
—
|
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: Heineken-branded merchandise | Statement: [Heineken Experience brewery, sells, Heineken-branded merchandise]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sells Context triple: [Heineken Experience brewery, sells, Heineken-branded merchandise]
-
A.
trades
Indicates an exchange relationship where one party gives something of value to another in return for something else of value.
-
B.
market
chosen
Indicates the act of promoting, advertising, or selling a product, service, or idea to potential buyers or target audiences.
-
C.
commodity
Indicates that one entity is a tradable good or resource that is bought, sold, or exchanged in relation to another entity.
-
D.
commercializedIn
Indicates that something has been brought to market or made available for commercial sale or use within a specified place or context.
-
E.
collects
Indicates that one entity gathers, accumulates, or brings together one or more other entities into its possession or control.
- 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_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. |
Created at: Feb. 28, 2026, 2:40 a.m.