Triple

T17234222
Position Surface form Disambiguated ID Type / Status
Subject Chrome Beta channel E418318 entity
Predicate stabilityComparedToCanary P126485 FINISHED
Object more stable 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: more stable | Statement: [Chrome Beta channel, stabilityComparedToCanary, more stable]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: stabilityComparedToCanary
Context triple: [Chrome Beta channel, stabilityComparedToCanary, more stable]
  • A. stableReleaseStatus
    Indicates the release status or condition of a stable version of something (such as software or a product).
  • B. isStable
    Indicates that the state, condition, or configuration of an entity does not change significantly over time or under expected variations in its environment.
  • C. hasStabilityLevel
    Indicates that something possesses a particular degree or state of stability, often quantified or categorized along a defined scale.
  • D. isUnstable
    Indicates that the subject lacks stability or consistency, often changing, fluctuating, or failing to remain in a steady state.
  • E. unstableCodename
    Indicates that the codename assigned to something is temporary, experimental, or subject to change and should not be relied on as final.
  • F. None of above. chosen

Provenance (4 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.
PDg Predicate description generation batch_69e3873f62108190966c4e741ebd548d completed April 18, 2026, 1:29 p.m.
Created at: April 10, 2026, 5:39 a.m.