Triple
T17234225
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chrome Beta channel |
E418318
|
entity |
| Predicate | positionInReleaseCycle |
P31722
|
FINISHED |
| Object | between Dev channel and Stable channel |
—
|
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: between Dev channel and Stable channel | Statement: [Chrome Beta channel, positionInReleaseCycle, between Dev channel and Stable channel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInReleaseCycle Context triple: [Chrome Beta channel, positionInReleaseCycle, between Dev channel and Stable channel]
-
A.
typicalReleaseCandidateCycleLength
Indicates the usual duration of time that a release candidate phase lasts within a development or release cycle.
-
B.
stageNameDuringRelease
Indicates the stage name an entity used specifically during the time of a particular release.
-
C.
positionInPlan
Indicates the specific place or ordering of an element within a larger plan or sequence of planned steps.
-
D.
evaluationCycle
Indicates the recurring period or sequence in which evaluations or assessments are conducted and reviewed.
-
E.
cyclePosition
chosen
Indicates the relative location or order of something within a repeating or cyclical sequence.
- 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_69d886d8e96081909870bff6c3d0bf09 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42dfa0a408190880804d463305867 |
completed | April 19, 2026, 1:20 a.m. |
| PD | Predicate disambiguation | batch_69e3832553ac819091aa917c84f755b6 |
completed | April 18, 2026, 1:12 p.m. |
Created at: April 10, 2026, 5:39 a.m.