Triple
T5479317
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 4380 |
E123431
|
entity |
| Predicate | definesComponent |
P55139
|
FINISHED |
| Object | Teredo relay |
E23864
|
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: Teredo relay | Statement: [RFC 4380, definesComponent, Teredo relay]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Teredo relay Context triple: [RFC 4380, definesComponent, Teredo relay]
-
A.
Teredo
chosen
Teredo is a tunneling protocol that enables IPv6 connectivity for devices on IPv4 networks, particularly those behind NAT.
-
B.
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.
-
C.
Bitnet Relay
Bitnet Relay was an early global chat and messaging system on the BITNET academic network that pioneered real-time online communication before modern IRC and internet chat services.
-
D.
Traversal Using Relays around NAT
Traversal Using Relays around NAT (TURN) is a network protocol that enables devices behind firewalls or NATs to communicate by relaying their traffic through an intermediate server.
-
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 (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_69bd4648883481909e9775d43300c5fa |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd9247a16c8190ac5a02534da48853 |
completed | March 20, 2026, 6:30 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bf6c7a61848190970a4e34696791eb |
completed | March 22, 2026, 4:13 a.m. |
Created at: March 20, 2026, 2:09 p.m.