Triple

T3420639
Position Surface form Disambiguated ID Type / Status
Subject Dev channel E72106 entity
Predicate relativePositionInChannelHierarchy P5163 FINISHED
Object between Canary and Beta channels 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 Canary and Beta channels | Statement: [Dev channel, relativePositionInChannelHierarchy, between Canary and Beta channels]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: relativePositionInChannelHierarchy
Context triple: [Dev channel, relativePositionInChannelHierarchy, between Canary and Beta channels]
  • A. positionInHierarchy chosen
    Indicates that one entity occupies a specific rank or level relative to another within an ordered hierarchy.
  • B. relativePosition
    Indicates the spatial relationship of one entity’s location with respect to another entity’s position.
  • C. positionInCascade
    Indicates the specific step or level an element occupies within an ordered cascade or sequence of dependent stages.
  • D. positionedRelativeTo
    Indicates that one entity’s spatial location is defined or described in relation to the position of another entity.
  • E. relativeLevel
    Indicates a comparative relationship specifying how one entity’s level, degree, or intensity of some property stands relative to that of 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_69ad85ad38e48190b7660c5118a35289 completed March 8, 2026, 2:20 p.m.
NER Named-entity recognition batch_69adb94eb9e8819087a525df4550914b completed March 8, 2026, 6 p.m.
PD Predicate disambiguation batch_69adadfea024819094b41a13bc004bda completed March 8, 2026, 5:12 p.m.
Created at: March 8, 2026, 3:15 p.m.