Triple

T29010883
Position Surface form Disambiguated ID Type / Status
Subject Line Printer Daemon protocol E736561 entity
Predicate supportsJobIdentification P203889 FINISHED
Object via control file fields — 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: via control file fields | Statement: [Line Printer Daemon protocol, supportsJobIdentification, via control file fields]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: supportsJobIdentification
Context triple: [Line Printer Daemon protocol, supportsJobIdentification, via control file fields]
  • A. identifiesWork
    Indicates that one entity recognizes or specifies another entity as a particular work (such as a creative, scholarly, or professional output) associated with it.
  • B. supportedByWork
    Indicates that one entity’s existence, validity, or outcome is backed, justified, or enabled by the work or efforts of another entity.
  • C. supportsIdentity
    Indicates that one entity upholds, validates, or reinforces the identity, self-concept, or role of another entity.
  • D. hasHRIdentifier
    Indicates that an entity is associated with a specific identifier used by a Human Resources system to uniquely reference it.
  • E. usedByJob
    Indicates that something (such as a resource, tool, or component) is utilized or consumed in the execution of a particular job or task.
  • 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_69f077eb81e88190ad9ff62cbb9f555e completed April 28, 2026, 9:03 a.m.
NER Named-entity recognition batch_6a023f290e3081909a465d6cfb79518a completed May 11, 2026, 8:42 p.m.
PD Predicate disambiguation batch_6a0238d1436c8190ab0251030b01902e completed May 11, 2026, 8:15 p.m.
PDg Predicate description generation batch_6a023f27f1608190bac5be9c4c67f527 completed May 11, 2026, 8:42 p.m.
Created at: April 28, 2026, 9:42 a.m.