Triple
T8470868
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Name Binding Protocol |
E200275
|
entity |
| Predicate | similarTo |
P4460
|
FINISHED |
| Object | NetBIOS Name Service |
E700876
|
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: NetBIOS Name Service | Statement: [Name Binding Protocol, similarTo, NetBIOS Name Service]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: NetBIOS Name Service Context triple: [Name Binding Protocol, similarTo, NetBIOS Name Service]
-
A.
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.
-
B.
NetBIOS API
chosen
The NetBIOS API is a legacy network programming interface that allows applications to communicate over local area networks using NetBIOS services for name resolution and session management.
-
C.
NetBEUI
NetBEUI is a small, fast, non-routable network protocol historically used on Microsoft LANs for simple file and printer sharing.
-
D.
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.
-
E.
NETCOM
NETCOM is a major U.S. Army command responsible for operating, securing, and managing the Army’s global enterprise network and communications infrastructure.
- 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_69ca831a4f348190bfdd09250e86ae35 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe4f234c481909534de6fd702f4cf |
completed | March 31, 2026, 3:14 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ce39f45c3081908ea50810f0a386d6 |
completed | April 2, 2026, 9:42 a.m. |
Created at: March 30, 2026, 6:11 p.m.