Triple
T9712344
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atril document viewer |
E235050
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | GNOME Document Viewer fork |
C24720
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: GNOME Document Viewer fork Context triple: [Atril document viewer, instanceOf, GNOME Document Viewer fork]
-
A.
GNOME component
A GNOME component is a modular software element within the GNOME desktop environment that provides specific functionality or services, such as panels, applets, libraries, or system tools, to create a cohesive user experience.
-
B.
GNOME application
chosen
A GNOME application is a software program designed to integrate with the GNOME desktop environment, following its human interface guidelines, technologies, and design principles to provide a consistent user experience.
-
C.
acrobat
An acrobat is a highly skilled performer who executes precise, physically demanding feats of balance, agility, and coordination, often in circus, stage, or aerial environments.
-
D.
Debian Project document
A Debian Project document is an official or semi-official written artifact produced within the Debian community that records policies, procedures, decisions, or technical information relevant to the development, governance, or use of the Debian operating system.
-
E.
extensible editor
An extensible editor is a text or code editing environment designed with a flexible architecture that allows users to add, modify, and integrate new features or behaviors through plugins, scripts, or configuration.
- F. None of above.
Provenance (1 batch)
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_69ca84cd8fa0819090a5e243ceb37003 |
completed | March 30, 2026, 2:12 p.m. |
Created at: March 30, 2026, 8:19 p.m.