Triple
T28505233
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atril |
E721348
|
entity |
| Predicate | defaultDocumentViewerFor |
P168204
|
FINISHED |
| Object | MATE desktop environment |
—
|
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: MATE desktop environment | Statement: [Atril, defaultDocumentViewerFor, MATE desktop environment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: defaultDocumentViewerFor Context triple: [Atril, defaultDocumentViewerFor, MATE desktop environment]
-
A.
defaultDoclet
Indicates that a particular documentation generator or style is designated as the default one to be used when none is explicitly specified.
-
B.
coreDocumentOf
Indicates that one entity serves as the primary or central document associated with, or defining, another entity.
-
C.
defaultBrowserOn
Indicates that a particular browser is set as the default browser on a given device or system.
-
D.
defaultAdapter
Indicates that one entity serves as the primary or standard adapter used by another entity in the absence of a specifically chosen alternative.
-
E.
viewerApplication
chosen
Indicates that an application is used to view, display, or render a particular resource or content.
- F. None of above.
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_69f01a5c072081908c7b04bcf6478da9 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f6fb19063c81909466b329655c8583 |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f969b4cc8190afb473a2d8b110bc |
completed | May 3, 2026, 7:29 a.m. |
Created at: April 28, 2026, 3:09 a.m.