Triple
T29689758
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hyperbola GNU/Linux-libre |
E751181
|
entity |
| Predicate | usesSystemd |
P164598
|
FINISHED |
| Object | no |
—
|
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: no | Statement: [Hyperbola GNU/Linux-libre, usesSystemd, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesSystemd Context triple: [Hyperbola GNU/Linux-libre, usesSystemd, no]
-
A.
isSystemdOptional
Indicates that the system or software can function correctly without requiring systemd, allowing it to run with or without systemd being present or enabled.
-
B.
offersSystemdOption
Indicates that one entity provides or exposes a specific systemd configuration option to another entity or context.
-
C.
isSystemdFree
chosen
Indicates that the subject operates without using the systemd init system or any of its components.
-
D.
usedBySystem
Indicates that something is utilized or operated by a particular system.
-
E.
usesInitSystem
Indicates that one entity employs or is based on a particular initialization (init) system to start and manage services or processes.
- 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_69f0d625b09481909b0b69aea1e846c8 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f7805ce6208190ac6dbd9c97989978 |
completed | May 3, 2026, 5:05 p.m. |
| PD | Predicate disambiguation | batch_69f77956ec648190ba4fb7e9d83fd107 |
completed | May 3, 2026, 4:35 p.m. |
Created at: April 28, 2026, 7:15 p.m.