Triple
T29406193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GNOME Archive Manager |
E745781
|
entity |
| Predicate | supportsCommandLineBackends |
P174393
|
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: [GNOME Archive Manager, supportsCommandLineBackends, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsCommandLineBackends Context triple: [GNOME Archive Manager, supportsCommandLineBackends, yes]
-
A.
supportsCommand
Indicates that one entity is capable of recognizing, accepting, or executing a specified command associated with another entity.
-
B.
usesBackendTools
chosen
Indicates that one entity relies on or operates tools, systems, or services that function on the backend to perform its tasks or provide its functionality.
-
C.
hasCommandLineInterface
Indicates that an entity provides or supports interaction through a command-line interface (CLI).
-
D.
hasBackend
Indicates that one entity functions as the backend or server-side component that supports or powers another entity.
-
E.
hasCommandSystem
Indicates that one entity possesses, uses, or is associated with a particular command or control system.
- 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_69f0a79eb7d081908c67197a5f347e68 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e0f3d88190a4ee7b0673f1ef90 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 28, 2026, 2:54 p.m.