Triple

T22375714
Position Surface form Disambiguated ID Type / Status
Subject searchfox.org E553146 entity
Predicate supportsProject P12986 FINISHED
Object SpiderMonkey NE NERFINISHED

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 | Statement: [searchfox.org, supportsProject, SpiderMonkey]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: SpiderMonkey
Context triple: [searchfox.org, supportsProject, SpiderMonkey]
  • A. SpiderMonkey chosen
    SpiderMonkey is Mozilla's open-source JavaScript engine, written in C/C++ and used primarily in the Firefox web browser.
  • B. Rhino JavaScript engine
    Rhino JavaScript engine is an open-source JavaScript implementation written in Java that runs on the JVM and is used to execute JavaScript code within Java-based environments.
  • 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. Hermes JavaScript engine
    Hermes JavaScript engine is a lightweight, high-performance JavaScript engine optimized for running React Native applications on mobile devices.
  • 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 (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.