Triple
T28828510
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Whistler Beta 1 |
E727977
|
entity |
| Predicate | intendedReleaseChannel |
P5095
|
FINISHED |
| Object | retail |
—
|
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: retail | Statement: [Whistler Beta 1, intendedReleaseChannel, retail]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedReleaseChannel Context triple: [Whistler Beta 1, intendedReleaseChannel, retail]
-
A.
releaseChannel
chosen
Indicates the distribution pathway or medium through which something (such as a product, update, or content) is made available or delivered to its recipients.
-
B.
targetRelease
Indicates the specific release or version that an item (such as a feature, fix, or component) is planned or designated to be delivered in.
-
C.
intendedForReleaseIn
Indicates that something is planned or scheduled to be made available or launched within a specified context, such as a time, market, or platform.
-
D.
releaseVersion
Indicates the specific version identifier associated with a particular release of something (e.g., software, product, or document).
-
E.
releaseCandidatePurpose
Indicates the intended purpose or goal for which a particular release candidate is created or used.
- 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_69f0319dc6088190bbfaa206d40ed74a |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f74c70fd248190a9d5543afcb08211 |
completed | May 3, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69f7478e3b548190a51d5d436e2bb036 |
completed | May 3, 2026, 1:03 p.m. |
Created at: April 28, 2026, 6:36 a.m.