Triple
T21191763
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 5214 |
E522227
|
entity |
| Predicate | protocol |
P1992
|
FINISHED |
| Object | ISATAP |
—
|
NE NERFINISHED |
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: ISATAP | Statement: [RFC 5214, protocol, ISATAP]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: ISATAP Context triple: [RFC 5214, protocol, ISATAP]
-
A.
ISATAP
chosen
ISATAP (Intra-Site Automatic Tunnel Addressing Protocol) is an IPv6 transition mechanism that enables IPv6 connectivity over an IPv4 intranet by encapsulating IPv6 packets within IPv4.
-
B.
Teredo
Teredo is a tunneling protocol that enables IPv6 connectivity for devices on IPv4 networks, particularly those behind NAT.
-
C.
NAT64
NAT64 is a network address translation mechanism that enables IPv6-only clients to communicate with IPv4 servers by translating between the two protocol address spaces and packet formats.
-
D.
IS-IS for IPv6
IS-IS for IPv6 is an extension of the IS-IS interior gateway routing protocol that enables dynamic routing and topology discovery in IPv6 networks.
-
E.
IEEE 802.1ah
IEEE 802.1ah is an Ethernet networking standard, often called Provider Backbone Bridges (PBB), that enables scalable, MAC-in-MAC encapsulation for carrier-grade layer 2 networks.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0b51061388190aa03f19700d3ef04 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e733381f288190b3da795f62a39568 |
completed | April 21, 2026, 8:20 a.m. |
Created at: April 16, 2026, 3:07 p.m.