Triple
T8413328
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Human68k |
E198673
|
entity |
| Predicate | supportsGraphicalEnvironment |
P32774
|
FINISHED |
| Object | yes |
—
|
LITERAL 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: yes | Statement: [Human68k, supportsGraphicalEnvironment, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsGraphicalEnvironment Context triple: [Human68k, supportsGraphicalEnvironment, yes]
-
A.
hasGraphicalInstaller
Indicates that an entity provides or supports a graphical (GUI-based) installation interface or process.
-
B.
usesVisualMotif
Indicates that one entity employs a recurring visual element or pattern as a motif in relation to another entity or context.
-
C.
hasDefaultDesktopEnvironment
chosen
Indicates that a particular desktop environment is the standard or preconfigured graphical interface for a given system or distribution.
-
D.
usesDisplayServer
Indicates that one entity relies on or operates through a display server provided or managed by another entity.
-
E.
usesGUIFramework
Indicates that one entity employs or is built upon a particular graphical user interface (GUI) framework to provide its visual or interactive functionality.
- 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_69ca831201b481909e137936ef99ff11 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cb83e18e7c8190a30b14136dee3d93 |
completed | March 31, 2026, 8:20 a.m. |
| PD | Predicate disambiguation | batch_69cb70d473dc8190af8ea81ee5aa970d |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 6:06 p.m.