Triple

T7895606
Position Surface form Disambiguated ID Type / Status
Subject Tencent QQ Browser (legacy Trident mode) E183335 entity
Predicate renderingMode P79636 FINISHED
Object Trident compatibility mode 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: Trident compatibility mode | Statement: [Tencent QQ Browser (legacy Trident mode), renderingMode, Trident compatibility mode]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: renderingMode
Context triple: [Tencent QQ Browser (legacy Trident mode), renderingMode, Trident compatibility mode]
  • A. renderingModel
    Indicates the specific rendering engine or model used to generate the visual or graphical output for an entity.
  • B. displayMode
    Indicates how content or information is visually presented or arranged to the user.
  • C. notableRendering
    Indicates that one entity is a significant or well-known visual or artistic depiction of another entity.
  • D. renders
    Indicates that one entity produces, generates, or visually presents another entity, often by transforming data or instructions into a final displayed or usable form.
  • E. renderedUnder
    Indicates that one entity was produced, displayed, or executed within the authority, context, or environment provided by another entity.
  • 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_69ca828c474c8190a254d6499871eaff completed March 30, 2026, 2:02 p.m.
NER Named-entity recognition batch_69cb3a174574819084270dbb6fcbb7fe completed March 31, 2026, 3:05 a.m.
PD Predicate disambiguation batch_69cae92d94448190b4425bbfb64c658c completed March 30, 2026, 9:20 p.m.
PDg Predicate description generation batch_69caf786ec748190b6347b0c94335550 completed March 30, 2026, 10:21 p.m.
Created at: March 30, 2026, 5:01 p.m.