Triple
T33735126
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | xinetd |
E864392
|
entity |
| Predicate | activationModel |
P58199
|
FINISHED |
| Object | on-demand service activation |
—
|
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: on-demand service activation | Statement: [xinetd, activationModel, on-demand service activation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: activationModel Context triple: [xinetd, activationModel, on-demand service activation]
-
A.
activationType
chosen
Indicates the specific manner or mechanism by which an activation or triggering event occurs between entities.
-
B.
activationBy
Indicates that one entity initiates, triggers, or enhances the activity, function, or state of another entity.
-
C.
activationNetwork
Indicates that one entity initiates, enhances, or enables the functional activity of another entity within a connected system or pathway.
-
D.
activationMechanism
Indicates the process or method by which one entity initiates, triggers, or enables the activity or functioning of another entity.
-
E.
activationStatus
Indicates whether an entity is currently active, enabled, or in effect within a given context.
- 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_69f3498a64cc8190b4b414c67b280d93 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7b5ccbda481908fe1945c35e36ce8 |
completed | May 3, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c06f5881908f0b98cad6796478 |
completed | May 3, 2026, 8:49 p.m. |
Created at: May 1, 2026, 1:44 a.m.