Triple

T9978237
Position Surface form Disambiguated ID Type / Status
Subject NTLM E196384 entity
Predicate usedBy P260 FINISHED
Object SMB protocol E37352 NE 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: SMB protocol | Statement: [NTLM, usedBy, SMB protocol]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: SMB protocol
Context triple: [NTLM, usedBy, SMB protocol]
  • A. SMB chosen
    SMB (Server Message Block) is a network file sharing protocol widely used in Windows environments to enable shared access to files, printers, and other network resources.
  • B. SMB
    SMB is the abbreviation for the IEC’s Standardization Management Board, the body responsible for overseeing and coordinating international electrotechnical standardization activities.
  • C. NetBIOS over TCP/IP
    NetBIOS over TCP/IP is a networking protocol that encapsulates NetBIOS services on top of the TCP/IP stack, enabling name resolution and session services across IP-based networks.
  • D. Microsoft RPC
    Microsoft RPC is a communication protocol framework developed by Microsoft that enables software components on different computers or processes to invoke each other’s procedures as if they were local.
  • E. NetWare Core Protocol
    NetWare Core Protocol is a network protocol used by Novell NetWare systems to provide file, print, and directory services over local area networks.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69ca82efbce081908179b4b9c65096eb completed March 30, 2026, 2:04 p.m.
NER Named-entity recognition batch_69cdb84ef8ac8190abbe78b7611c5309 completed April 2, 2026, 12:29 a.m.
NED1 Entity disambiguation (via context triple) batch_69d23dec07b48190a2c15a748324291b completed April 5, 2026, 10:48 a.m.
Created at: March 30, 2026, 8:49 p.m.