Triple
T33735128
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | xinetd |
E864392
|
entity |
| Predicate | controlsServiceType |
P197210
|
FINISHED |
| Object | network daemons |
—
|
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: network daemons | Statement: [xinetd, controlsServiceType, network daemons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: controlsServiceType Context triple: [xinetd, controlsServiceType, network daemons]
-
A.
controlsType
Indicates that one entity has authority over, or the ability to direct or regulate, the type or category of another entity.
-
B.
controlsDeviceType
Indicates that an entity has authority over or can operate a specific type or category of device.
-
C.
connectsServiceType
Indicates a relationship where one entity is linked or associated to another based on a specific type of service connection.
-
D.
controlsSystem
Indicates that one entity has the authority or capability to direct, manage, or regulate the operation of a system.
-
E.
controlDeviceTypical
Indicates that an entity typically operates or manages the functioning of a device.
- 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_69f3498a64cc8190b4b414c67b280d93 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fe7bfc94bc81909eeec946e8c1c450 |
completed | May 9, 2026, 12:12 a.m. |
| PD | Predicate disambiguation | batch_69fe7b74a1188190886f128e07f712da |
completed | May 9, 2026, 12:10 a.m. |
| PDg | Predicate description generation | batch_69fe7bfb71b08190bed5c33e4ab7afff |
completed | May 9, 2026, 12:12 a.m. |
Created at: May 1, 2026, 1:44 a.m.