Triple
T1866670
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 826 |
E34936
|
entity |
| Predicate | usedBy |
P260
|
FINISHED |
| Object | IPv4 |
E1269
|
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: IPv4 | Statement: [RFC 826, usedBy, IPv4]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: IPv4 Context triple: [RFC 826, usedBy, IPv4]
-
A.
IPv4
chosen
IPv4 is the fourth version of the Internet Protocol, providing a 32-bit address space that underpins most of today’s internet routing and communication.
-
B.
Internet Protocol version 6
Internet Protocol version 6 (IPv6) is the modern Internet addressing and routing protocol designed to replace IPv4 by providing a vastly larger address space and improved network efficiency and security features.
-
C.
Internet Protocol
Internet Protocol is the core networking protocol that defines how data packets are addressed and routed across interconnected computer networks, forming the foundation of the modern internet.
-
D.
TCP/IP
TCP/IP is the fundamental communication protocol suite that enables data transmission and networking across the internet and most modern computer networks.
-
E.
ICMP
ICMP (Internet Control Message Protocol) is a core network-layer protocol used primarily for sending error messages and operational information, such as in tools like ping and traceroute, within IP 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_69a88600b2f88190bc09303e68ab517e |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69abb0b5978c81909390f2cbd716ccaf |
completed | March 7, 2026, 4:59 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69addf5163d88190a41df4c8f4e196f0 |
completed | March 8, 2026, 8:42 p.m. |
Created at: March 4, 2026, 7:34 p.m.