Triple
T26879180
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Red Bull Winter Edition |
E676841
|
entity |
| Predicate | availabilityPattern |
P161976
|
FINISHED |
| Object | limited distribution period |
—
|
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: limited distribution period | Statement: [Red Bull Winter Edition, availabilityPattern, limited distribution period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: availabilityPattern Context triple: [Red Bull Winter Edition, availabilityPattern, limited distribution period]
-
A.
availabilityPattern
chosen
Indicates a recurring schedule or pattern that defines when something is available or unavailable over time.
-
B.
availabilityModel
Indicates how and under what conditions an entity is available for use, access, or interaction.
-
C.
availability
Indicates that an entity is present, accessible, or ready for use or interaction by another entity.
-
D.
availabilityStart
Indicates the date and time from which something becomes available or active.
-
E.
availabilityType
Indicates the specific way in which something is available or offered (e.g., its mode, status, or conditions of availability) in relation to another entity.
- 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_69eee9bb44988190b6e11652d028bc59 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f621cbc48881908d104c648c91c715 |
completed | May 2, 2026, 4:09 p.m. |
| PD | Predicate disambiguation | batch_69f620e0b37481909a280574decbd443 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 5:38 a.m.