Triple
T27755153
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | System V init |
E701315
|
entity |
| Predicate | startupOrderMechanism |
P189987
|
FINISHED |
| Object | script name prefixes such as SNNservice |
—
|
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: script name prefixes such as SNNservice | Statement: [System V init, startupOrderMechanism, script name prefixes such as SNNservice]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startupOrderMechanism Context triple: [System V init, startupOrderMechanism, script name prefixes such as SNNservice]
-
A.
startingSystem
Indicates the system or context from which an action, process, or transition is initially begun.
-
B.
schedulingMechanism
chosen
Indicates the method or process by which activities, tasks, or events are organized and assigned specific times or sequences.
-
C.
startOrderDeterminedBy
Indicates that the point in time or sequence at which something begins is determined or constrained by another specified factor or event.
-
D.
establishedInOrder
Indicates that one entity was created, founded, or formally set up as a result of, or in accordance with, a specific order, directive, or mandate.
-
E.
selectionOrderAdjustment
Indicates a modification to the original order in which items or options were selected, such as reordering or adjusting their selection sequence.
- 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_69ef6a5193808190816eb7d0020b2d87 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69fd2a215d6c8190a1a428ccaee603f1 |
completed | May 8, 2026, 12:11 a.m. |
| PD | Predicate disambiguation | batch_69fd28ef19688190bb8370f2812a43e7 |
completed | May 8, 2026, 12:06 a.m. |
Created at: April 27, 2026, 4:23 p.m.