Triple
T21191699
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 6081 |
E522225
|
entity |
| Predicate | defines |
P264
|
FINISHED |
| Object | Teredo extensions |
—
|
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: Teredo extensions | Statement: [RFC 6081, defines, Teredo extensions]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Teredo extensions Context triple: [RFC 6081, defines, Teredo extensions]
-
A.
Teredo
chosen
Teredo is a tunneling protocol that enables IPv6 connectivity for devices on IPv4 networks, particularly those behind NAT.
-
B.
ISATAP
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.
-
C.
NAT-T
NAT-T (NAT Traversal) is an IPsec extension that enables VPN traffic to pass through Network Address Translation devices by encapsulating IPsec packets in UDP.
-
D.
IPv6 extension headers
IPv6 extension headers are optional, chained header fields in IPv6 packets that provide additional functionality such as routing, fragmentation, security, and quality-of-service beyond the basic IPv6 header.
-
E.
TUN
TUN is the three-letter ISO 3166-1 alpha-3 country code assigned to Tunisia.
- 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.