Triple
T5716663
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 1195 |
E126039
|
entity |
| Predicate | obsoletedBy |
P101
|
FINISHED |
| Object | RFC 5308 |
E130003
|
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: RFC 5308 | Statement: [RFC 1195, obsoletedBy, RFC 5308]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 5308 Context triple: [RFC 1195, obsoletedBy, RFC 5308]
-
A.
RFC 5308
chosen
RFC 5308 is the Internet Engineering Task Force (IETF) specification that extends the IS-IS routing protocol to support IPv6 addressing and routing.
-
B.
RFC 5338
RFC 5338 is an Internet Engineering Task Force (IETF) document that specified an earlier approach to managing the IANA IPv6 Special-Purpose Address Registry before being superseded by a later standard.
-
C.
RFC 5702
RFC 5702 is an Internet standards document that specifies the use of SHA-2 family hash algorithms with DNSSEC to enhance the security of DNS authentication.
-
D.
RFC 3948
RFC 3948 is an IETF standard that specifies how to encapsulate IPsec ESP packets over UDP to enable IPsec traversal through NAT devices.
-
E.
RFC 4380
RFC 4380 is an IETF standard that specifies the Teredo protocol for providing IPv6 connectivity to nodes located behind IPv4 network address translators (NATs).
- 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_69c0082e3d548190950169847b43043b |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c024ba819c8190bb7d775405dda9d6 |
completed | March 22, 2026, 5:19 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c05a7af5788190827ff8050eb6416d |
completed | March 22, 2026, 9:09 p.m. |
Created at: March 22, 2026, 3:46 p.m.