Triple

T29440470
Position Surface form Disambiguated ID Type / Status
Subject RFC 8011 E746696 entity
Predicate definesTransportUsage P175205 FINISHED
Object IPP over HTTP
IPP over HTTP is a network printing protocol that enables Internet Printing Protocol (IPP) operations to be carried over standard HTTP connections for managing print jobs and printers.
 E1867818 NE FINISHED

How this triple was built (3 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: IPP over HTTP | Statement: [RFC 8011, definesTransportUsage, IPP over HTTP]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: IPP over HTTP
Triple: [RFC 8011, definesTransportUsage, IPP over HTTP]
Generated description
IPP over HTTP is a network printing protocol that enables Internet Printing Protocol (IPP) operations to be carried over standard HTTP connections for managing print jobs and printers.
PD Predicate disambiguation gpt-5-mini-2025-08-07 
Target predicate: definesTransportUsage
Context triple: [RFC 8011, definesTransportUsage, IPP over HTTP]
  • A. definesTransportFor chosen
    Indicates that one entity specifies or determines the means, method, or system of transport used by another entity.
  • B. usesTransport
    Indicates that an entity employs or relies on a particular mode or means of transportation to move from one place to another.
  • C. transportInterface
    Indicates a relationship where one entity serves as the medium or mechanism through which another entity is transported or conveyed.
  • D. passesUsedForTransportation
    Indicates that the passes are utilized as a means or instrument for transporting people or goods.
  • E. usesTransportNetwork
    Indicates that an entity makes use of a transport network (such as roads, rail, or transit systems) to move people, goods, or services.
  • F. None of above.

Provenance (6 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_69f0a7a180e48190ae775e40047dbcb5 completed April 28, 2026, 12:27 p.m.
NER Named-entity recognition batch_69fcef654d588190b29ecc76678d1aa0 completed May 7, 2026, 8 p.m.
NED1 Entity disambiguation (via context triple) batch_6a25d936933c81908e814d5efe547b29 completed June 7, 2026, 8:48 p.m.
NEDg Description generation batch_6a25dd39b5e08190afdacb75ea8ef091 completed June 7, 2026, 9:06 p.m.
NED2 Entity disambiguation (via description) batch_6a25e28ca1988190929154c0ceb6d42b completed June 7, 2026, 9:28 p.m.
PD Predicate disambiguation batch_69fcecdb97f48190b382b7d13be92dc0 completed May 7, 2026, 7:49 p.m.
Created at: April 28, 2026, 3:21 p.m.