Triple
T29010868
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Line Printer Daemon protocol |
E736561
|
entity |
| Predicate | usesClientProgram |
P180024
|
FINISHED |
| Object | lpr |
—
|
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: lpr | Statement: [Line Printer Daemon protocol, usesClientProgram, lpr]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesClientProgram Context triple: [Line Printer Daemon protocol, usesClientProgram, lpr]
-
A.
hasClientProgram
chosen
Indicates that an entity (such as a service, system, or organization) is associated with or uses a specific client program.
-
B.
usedByProgram
Indicates that a particular resource, component, or element is utilized or consumed by a specific program.
-
C.
usedProgramModel
Indicates that an entity employed a specific program model as the basis or framework for its activities or operations.
-
D.
usedAsProgramFor
Indicates that one entity functions as the software or application used to operate, control, or provide services for another entity.
-
E.
programUsed
Indicates that a particular program, software, or application was employed or utilized in performing an action or achieving a result.
- 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_69f077eb81e88190ad9ff62cbb9f555e |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f75dc25fa08190b371faf36d9fb72c |
completed | May 3, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f758586534819083e91172f4bf5098 |
completed | May 3, 2026, 2:14 p.m. |
Created at: April 28, 2026, 9:42 a.m.