Triple

T5895387
Position Surface form Disambiguated ID Type / Status
Subject Mozilla JavaScript team E131087 entity
Predicate produces P490 FINISHED
Object SpiderMonkey bytecode interpreter E24484 NE 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: SpiderMonkey bytecode interpreter | Statement: [Mozilla JavaScript team, produces, SpiderMonkey bytecode interpreter]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: SpiderMonkey bytecode interpreter
Context triple: [Mozilla JavaScript team, produces, SpiderMonkey bytecode interpreter]
  • A. SpiderMonkey chosen
    SpiderMonkey is Mozilla's open-source JavaScript engine, written in C/C++ and used primarily in the Firefox web browser.
  • B. Hermes JavaScript engine
    Hermes JavaScript engine is a lightweight, high-performance JavaScript engine optimized for running React Native applications on mobile devices.
  • C. Nashorn
    Nashorn was a German World War II tank destroyer armed with a powerful 88 mm gun and built on a modified Panzer IV chassis.
  • D. JSBC
    JSBC is the commonly used abbreviation for the Jersey Shore BlueClaws, a Minor League Baseball team based in New Jersey.
  • E. JavaScriptCore
    JavaScriptCore is Apple’s high-performance JavaScript engine used primarily in the Safari web browser and WebKit-based applications.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69c00857439c819095950754176aa58a completed March 22, 2026, 3:18 p.m.
NER Named-entity recognition batch_69c036f3364c81909353f62ca483f24f completed March 22, 2026, 6:37 p.m.
NED1 Entity disambiguation (via context triple) batch_69c1134bb82881908b912f96a3b6f0f1 completed March 23, 2026, 10:17 a.m.
Created at: March 22, 2026, 3:58 p.m.