Triple
T11957708
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | wlroots |
E284594
|
entity |
| Predicate | supportsRenderingAPI |
P22768
|
FINISHED |
| Object | EGL |
E724171
|
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: EGL | Statement: [wlroots, supportsRenderingAPI, EGL]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: EGL Context triple: [wlroots, supportsRenderingAPI, EGL]
-
A.
EGL
EGL is the station code used to identify Eglinton station in transit systems and related services.
-
B.
EGL
chosen
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.
-
C.
EGLC
EGLC is the ICAO airport code for London City Airport, a central London hub known for its short runway and business-focused flights.
-
D.
EGLF
EGLF is the ICAO airport code for Farnborough Airport, a major business aviation hub in Hampshire, England.
-
E.
OpenGL ES
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.
- 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_69d6ab2db38c8190b1f0ed6663ef8ada |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d903681a00819098c2b5260e2ef834 |
completed | April 10, 2026, 2:04 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f471c931a88190a9d29262c62b9472 |
completed | May 1, 2026, 9:26 a.m. |
Created at: April 8, 2026, 9:45 p.m.