Triple
T22461806
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Absolut Vodka |
E555247
|
entity |
| Predicate | introducedToUSMarket |
P36110
|
FINISHED |
| Object | 1979 |
—
|
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: 1979 | Statement: [Absolut Vodka, introducedToUSMarket, 1979]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedToUSMarket Context triple: [Absolut Vodka, introducedToUSMarket, 1979]
-
A.
introducedInMarket
chosen
Indicates that an entity was first made available or launched for sale within a particular market or marketplace.
-
B.
firstAiredInMarket
Indicates the date or time when a piece of content was initially broadcast or released in a specific market or region.
-
C.
launchedInCountry
Indicates that an entity (such as a product, service, or mission) was officially initiated, introduced, or started within a specified country.
-
D.
marketedFor
Indicates that something is promoted, advertised, or positioned as being intended or suitable for a particular use, audience, or purpose.
-
E.
introducedTo
Indicates that one entity caused or facilitated a first meeting or formal presentation between another entity and a third party.
- 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_69e11e51fdec8190adfdf9f8a6362221 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15b7f74948190beaf6ea24ba29276 |
completed | April 29, 2026, 1:14 a.m. |
| PD | Predicate disambiguation | batch_69e898ad961c819098fd1e46129bddcc |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:48 p.m.