Triple
T9312125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | daemontools |
E224029
|
entity |
| Predicate | restartPolicy |
P88022
|
FINISHED |
| Object | automatic restart on exit by supervise |
—
|
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: automatic restart on exit by supervise | Statement: [daemontools, restartPolicy, automatic restart on exit by supervise]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: restartPolicy Context triple: [daemontools, restartPolicy, automatic restart on exit by supervise]
-
A.
stopPolicy
Indicates that an entity terminates, cancels, or brings to an end a policy or ongoing course of action.
-
B.
terminationPolicyApplied
Indicates that a specific termination policy has been enforced or put into effect for the related entity or relationship.
-
C.
terminationPolicyEnded
Indicates that a previously established termination policy has come to an end and is no longer in effect.
-
D.
trackingPolicy
Indicates a relationship where one party defines or applies rules governing how another party’s activities, data, or movements are monitored and recorded.
-
E.
reignRestart
Indicates that a ruler’s period of governance has begun again after an interruption or previous end.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69cc955a38108190b602d1e73725f11b |
completed | April 1, 2026, 3:47 a.m. |
Created at: March 30, 2026, 7:37 p.m.