Triple
T28506360
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | antiX |
E721373
|
entity |
| Predicate | usesInitScripts |
P31192
|
FINISHED |
| Object | SysV-style init scripts |
—
|
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: SysV-style init scripts | Statement: [antiX, usesInitScripts, SysV-style init scripts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesInitScripts Context triple: [antiX, usesInitScripts, SysV-style init scripts]
-
A.
usesScriptFor
Indicates that one entity employs or relies on a particular script or writing system for its representation, communication, or operation.
-
B.
usesInitSystem
chosen
Indicates that one entity employs or is based on a particular initialization (init) system to start and manage services or processes.
-
C.
containsScript
Indicates that one entity includes or embeds the script of another entity within it.
-
D.
laterUsedScript
Indicates that one entity adopted or employed the script of another entity at a later point in time.
-
E.
usesScriptDerivedFrom
Indicates that one entity employs a writing system that is historically or structurally derived from the script used by another entity.
- 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_69f652a492108190b885b955ce147d3c |
completed | May 2, 2026, 7:38 p.m. |
| PD | Predicate disambiguation | batch_69f651aad92c8190b874b3b5f9f64434 |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 28, 2026, 3:09 a.m.