Triple
T63865
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IPv4 |
E1269
|
entity |
| Predicate | successor |
P78
|
FINISHED |
| Object | IPv6 |
E4018
|
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: IPv6 | Statement: [IPv4, successor, IPv6]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: IPv6 Context triple: [IPv4, successor, IPv6]
-
A.
Internet Protocol version 6
chosen
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.
-
B.
IPv4
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.
-
C.
TCP/IP
TCP/IP is the fundamental communication protocol suite that enables data transmission and networking across the internet and most modern computer networks.
-
D.
ARPANET
ARPANET was the pioneering packet-switching network developed in the late 1960s that became the technical foundation of the modern Internet.
-
E.
IEEE 802.1Q VLAN tagging standard
The IEEE 802.1Q VLAN tagging standard defines how virtual LANs are implemented and identified over Ethernet networks by inserting a VLAN tag into Ethernet frames.
- 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_69a24ba4f760819081f6638a3c70538a |
completed | Feb. 28, 2026, 1:57 a.m. |
| NER | Named-entity recognition | batch_69a24ee576fc8190b42e5d50767beefb |
completed | Feb. 28, 2026, 2:11 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a2554c4edc8190a44fa66848c5f738 |
completed | Feb. 28, 2026, 2:39 a.m. |
Created at: Feb. 28, 2026, 2:02 a.m.