Triple

T8859898
Position Surface form Disambiguated ID Type / Status
Subject AppleTalk Phase 2 E210859 entity
Predicate configurationProtocol P85043 FINISHED
Object AURP-compatible in some implementations 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: AURP-compatible in some implementations | Statement: [AppleTalk Phase 2, configurationProtocol, AURP-compatible in some implementations]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: configurationProtocol
Context triple: [AppleTalk Phase 2, configurationProtocol, AURP-compatible in some implementations]
  • A. managementProtocol
    Indicates the specific procedures, rules, or methods that govern how a particular process, resource, or situation is managed or administered.
  • B. protocolName
    Indicates the specific communication or interaction protocol used or associated with an entity or connection.
  • C. transportProtocol
    Indicates the communication protocol used to transport data between entities in a networked interaction.
  • D. protocolVersion
    Indicates the specific version of a protocol that governs how two or more entities communicate or interact.
  • E. protocolNumber
    Indicates the specific identifying number assigned to a protocol that governs or documents an interaction, process, or agreement between entities.
  • 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_69ca838bbddc8190ab546d737e5d350f completed March 30, 2026, 2:07 p.m.
NER Named-entity recognition batch_69cc60e712d08190bfb1c4ba3acaea90 completed April 1, 2026, 12:03 a.m.
PD Predicate disambiguation batch_69cc5c279ea481908c71756f694b66bf completed March 31, 2026, 11:43 p.m.
PDg Predicate description generation batch_69cc5cffe8ec819084c12770fe0578f2 completed March 31, 2026, 11:47 p.m.
Created at: March 30, 2026, 6:50 p.m.