Triple

T22375840
Position Surface form Disambiguated ID Type / Status
Subject Mozilla performance team E553148 entity
Predicate collaboratesWith P37 FINISHED
Object Firefox engineering teams — NE NERFINISHED

How this triple was built (3 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: Firefox engineering teams | Statement: [Mozilla performance team, collaboratesWith, Firefox engineering teams]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: Firefox engineering teams
Context triple: [Mozilla performance team, collaboratesWith, Firefox engineering teams]
  • A. Mozilla JavaScript team
    The Mozilla JavaScript team is the group within Mozilla responsible for developing and maintaining the SpiderMonkey JavaScript engine used in Firefox and other Mozilla projects.
  • B. Mozilla performance team
    The Mozilla performance team is a specialized group at Mozilla focused on measuring, analyzing, and improving the speed, responsiveness, and resource efficiency of Mozilla’s products and technologies.
  • C. Mozilla security team
    The Mozilla security team is the group within Mozilla responsible for safeguarding its products and infrastructure by identifying, analyzing, and mitigating security vulnerabilities.
  • D. Mozilla platform
    Mozilla platform is the underlying application and rendering framework developed by Mozilla, providing core technologies such as the Gecko engine and related components for building cross-platform software.
  • E. Google Chrome team
    The Google Chrome team is the group at Google responsible for developing, maintaining, and improving the Chrome web browser and its related channels and features.
  • F. None of above. chosen
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07 
Target entity: Firefox engineering teams
Target entity description: Firefox engineering teams are the groups of software engineers at Mozilla responsible for developing, maintaining, and improving the Firefox web browser’s features, performance, and architecture.
  • A. Mozilla JavaScript team
    The Mozilla JavaScript team is the group within Mozilla responsible for developing and maintaining the SpiderMonkey JavaScript engine used in Firefox and other Mozilla projects.
  • B. Mozilla performance team
    The Mozilla performance team is a specialized group at Mozilla focused on measuring, analyzing, and improving the speed, responsiveness, and resource efficiency of Mozilla’s products and technologies.
  • C. Mozilla security team
    The Mozilla security team is the group within Mozilla responsible for safeguarding its products and infrastructure by identifying, analyzing, and mitigating security vulnerabilities.
  • D. Mozilla platform
    Mozilla platform is the underlying application and rendering framework developed by Mozilla, providing core technologies such as the Gecko engine and related components for building cross-platform software.
  • E. Google Chrome team
    The Google Chrome team is the group at Google responsible for developing, maintaining, and improving the Chrome web browser and its related channels and features.
  • F. None of above. chosen

Provenance (2 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_69e11e4c03248190a26a5060ea6973ee completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f15807cb748190abd9adc08ca1ad4f completed April 29, 2026, 12:59 a.m.
Created at: April 16, 2026, 8:45 p.m.