Triple
T264964
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Internet Explorer |
E5702
|
entity |
| Predicate | supports |
P516
|
FINISHED |
| Object | JavaScript |
E3742
|
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: JavaScript | Statement: [Internet Explorer, supports, JavaScript]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: JavaScript Context triple: [Internet Explorer, supports, JavaScript]
-
A.
JavaScript
chosen
JavaScript is a high-level, dynamic programming language primarily used to create interactive and dynamic content on web pages.
-
B.
ECMAScript
ECMAScript is the official scripting language specification that defines the core features and behavior implemented by JavaScript and related languages.
-
C.
JScript .NET
JScript .NET is a Microsoft-developed scripting language that extends JScript with .NET Framework features, enabling object-oriented programming and integration with the .NET runtime.
-
D.
Node.js
Node.js is an open-source, cross-platform runtime environment that allows developers to execute JavaScript code on the server side.
-
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_69a2587daeb081909591b9d30f80a271 |
completed | Feb. 28, 2026, 2:52 a.m. |
| NER | Named-entity recognition | batch_69a25d8f9bbc8190a13841e4de093a66 |
completed | Feb. 28, 2026, 3:14 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a38b8e36b481909f9a039236e663df |
completed | March 1, 2026, 12:42 a.m. |
Created at: Feb. 28, 2026, 2:56 a.m.