Triple

T17568025
Position Surface form Disambiguated ID Type / Status
Subject Mozilla Quantum project E427866 entity
Predicate targetedPlatform P43193 FINISHED
Object desktop web browsers 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: desktop web browsers | Statement: [Mozilla Quantum project, targetedPlatform, desktop web browsers]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: targetedPlatform
Context triple: [Mozilla Quantum project, targetedPlatform, desktop web browsers]
  • A. platforms
    Indicates that one entity provides or serves as a base, medium, or environment that supports the operation, distribution, or presentation of another entity.
  • B. targetPlatformFeature
    Indicates that a particular feature is available on, or specifically associated with, a given target platform.
  • C. hasTargetPlatform chosen
    Indicates that something is intended to run on, be compatible with, or be deployed to a specified platform.
  • D. targetedDevice
    Indicates that one entity is the specific device toward which another entity’s action, effect, or configuration is directed.
  • E. consideredPlatform
    Indicates that one entity is regarded or treated as a platform (e.g., a base, medium, or environment) for another entity or activity.
  • 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_69d889e0385081908a04b66f4dd4bd0d completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e4592e56e481909249b831cecc31d5 completed April 19, 2026, 4:25 a.m.
PD Predicate disambiguation batch_69e3b4fd7d048190b54ee4c6155612a5 completed April 18, 2026, 4:44 p.m.
Created at: April 10, 2026, 5:50 a.m.