Triple
T14423480
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Web Graphics Library |
E357638
|
entity |
| Predicate | relatedStandard |
P37
|
FINISHED |
| Object | OpenGL ES |
E266145
|
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: OpenGL ES | Statement: [Web Graphics Library, relatedStandard, OpenGL ES]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: OpenGL ES Context triple: [Web Graphics Library, relatedStandard, OpenGL ES]
-
A.
OpenGL ES
chosen
OpenGL ES is a cross-platform, royalty-free 2D and 3D graphics API designed for embedded systems such as mobile devices, game consoles, and automotive displays.
-
B.
OpenGL
OpenGL is a cross-language, cross-platform application programming interface (API) for rendering 2D and 3D vector graphics, widely used in games, simulations, and professional visualization.
-
C.
EGL
EGL is the station code used to identify Eglinton station in transit systems and related services.
-
D.
EGL
EGL is an interface between Khronos rendering APIs like OpenGL ES and the native windowing system, enabling efficient rendering and context management on a variety of platforms.
-
E.
OpenGL SC
OpenGL SC is a safety-critical profile of the OpenGL graphics API designed for use in high-reliability, real-time, and embedded systems such as avionics and automotive 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_69d82793421c8190861eb0e673b085de |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de91123f848190ba3fb18a76c2d24c |
completed | April 14, 2026, 7:10 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd7a38003c819083f276fcaae52da9 |
completed | May 8, 2026, 5:52 a.m. |
Created at: April 10, 2026, 1:18 a.m.