Triple
T7366490
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 5338 |
E169882
|
entity |
| Predicate | hasAbbreviation |
P43
|
FINISHED |
| Object | RFC 5338 |
E169882
|
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 5338 | Statement: [RFC 5338, hasAbbreviation, RFC 5338]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 5338 Context triple: [RFC 5338, hasAbbreviation, RFC 5338]
-
A.
RFC 5338
chosen
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.
-
B.
RFC 5838
RFC 5838 is an IETF specification that updates and extends OSPFv3 to support multiple address families, including IPv4 and IPv6, within a single protocol instance.
-
C.
RFC 5382
RFC 5382 is an IETF specification that defines Network Address Translation (NAT) behavioral requirements for TCP to improve application compatibility and interoperability across NAT devices.
-
D.
RFC 5308
RFC 5308 is the Internet Engineering Task Force (IETF) specification that extends the IS-IS routing protocol to support IPv6 addressing and routing.
-
E.
RFC 5508
RFC 5508 is an Internet Engineering Task Force (IETF) standards document that specifies requirements and mechanisms related to IP networking, later refined and updated by RFC 6146.
- 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_69c68a5ade988190885b7175f63b7534 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f163038481909dedbffb4ae7f860 |
completed | March 27, 2026, 9:06 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c7fab9820c8190aa8b519a0852af6e |
completed | March 28, 2026, 3:58 p.m. |
Created at: March 27, 2026, 3:06 p.m.