Triple
T9312124
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | daemontools |
E224029
|
entity |
| Predicate | startMechanism |
P38751
|
FINISHED |
| Object | svscan scanning service directories |
—
|
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: svscan scanning service directories | Statement: [daemontools, startMechanism, svscan scanning service directories]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startMechanism Context triple: [daemontools, startMechanism, svscan scanning service directories]
-
A.
launchMechanism
Indicates the mechanism or system used to initiate or propel a launch of an object or process.
-
B.
driveMechanism
Indicates the mechanism or component that transmits power to drive or actuate another part of a system.
-
C.
activationMechanism
chosen
Indicates the process or method by which one entity initiates, triggers, or enables the activity or functioning of another entity.
-
D.
loadingMechanism
Indicates the method or system by which something is loaded into or onto another object or structure.
-
E.
openingMechanism
Indicates the method or mechanism by which an object or structure is opened or made accessible.
- 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_69ca8425f4fc81909c1c586e9a5b7530 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd20ae96e481909a1af9ea1c91f2b2 |
completed | April 1, 2026, 1:42 p.m. |
| PD | Predicate disambiguation | batch_69cc7a61e9a4819096eb014f3791ef2e |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:37 p.m.