Triple

T29285017
Position Surface form Disambiguated ID Type / Status
Subject Gateways, architectures, and Telnet protocol E742485 entity
Predicate protocolDiscussed P166793 FINISHED
Object Telnet NE NERFINISHED

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: Telnet | Statement: [Gateways, architectures, and Telnet protocol, protocolDiscussed, Telnet]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: protocolDiscussed
Context triple: [Gateways, architectures, and Telnet protocol, protocolDiscussed, Telnet]
  • A. protocol
    Indicates that one entity defines or follows a specific set of rules or procedures governing how it interacts or communicates with another entity.
  • B. protocolUse
    Indicates that an entity employs or relies on a specific protocol to perform a communication, interaction, or operation.
  • C. protocols
    Indicates that one entity defines, uses, or adheres to a specified set of rules or procedures governing how it interacts or communicates with another entity.
  • D. protocolDefined
    Indicates that a specific protocol formally specifies or governs the behavior, format, or interaction associated with the related entities.
  • E. protocolName
    Indicates the specific communication or interaction protocol used or associated with an entity or connection.
  • 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_69f09121ed8c8190b4cb27be3619c262 completed April 28, 2026, 10:51 a.m.
NER Named-entity recognition batch_69f665191d888190b4ab2c4bbd7725cb completed May 2, 2026, 8:56 p.m.
PD Predicate disambiguation batch_69f660f2e3708190ab658652bcfc04d0 completed May 2, 2026, 8:39 p.m.
PDg Predicate description generation batch_69f661e9cb308190a56e25dc17df248e completed May 2, 2026, 8:43 p.m.
Created at: April 28, 2026, 12:57 p.m.