Triple
T1717607
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Debian |
E37324
|
entity |
| Predicate | hasInitSystem |
P7431
|
FINISHED |
| Object | systemd (default on most architectures) |
—
|
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: systemd (default on most architectures) | Statement: [Debian, hasInitSystem, systemd (default on most architectures)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInitSystem Context triple: [Debian, hasInitSystem, systemd (default on most architectures)]
-
A.
hasInitial
Indicates that one entity possesses or is associated with the first letter or starting character of another entity’s name or value.
-
B.
hasCoreState
Indicates that an entity possesses or is associated with a fundamental or primary state that defines its core condition or behavior.
-
C.
hasAspectSystem
chosen
Indicates that an entity possesses or is associated with a particular aspect system, such as a structured set of characteristics, dimensions, or perspectives.
-
D.
hasOnboardSystems
Indicates that an entity is equipped with or contains specific onboard systems or subsystems.
-
E.
hasRegister
Indicates that one entity possesses, contains, or is associated with a specific register (such as a record, log, or hardware register).
- 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_69a8861912dc8190931af43b4b9158a7 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69ab5c96db6c8190a745d6fef7bf2cdb |
completed | March 6, 2026, 11 p.m. |
| PD | Predicate disambiguation | batch_69aa61bed2fc819086d912cd34285978 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:30 p.m.