Triple
T22027168
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IETF BEHAVE working group |
E543996
|
entity |
| Predicate | produced |
P490
|
FINISHED |
| Object | RFC 5780 |
—
|
NE NERFINISHED |
How this triple was built (3 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 5780 | Statement: [IETF BEHAVE working group, produced, RFC 5780]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 5780 Context triple: [IETF BEHAVE working group, produced, RFC 5780]
-
A.
RFC 5080
RFC 5080 is an IETF standards-track document that provides clarifications and implementation guidelines for the Remote Authentication Dial-In User Service (RADIUS) protocol and related extensions.
-
B.
RFC 5890
RFC 5890 is an Internet Engineering Task Force (IETF) standard that defines the terminology and concepts for Internationalized Domain Names (IDNs) in the Domain Name System (DNS).
-
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 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 5620
RFC 5620 is an IETF standards document that defines a framework for managing and monitoring MPLS-based transport networks.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: RFC 5780 Target entity description: RFC 5780 is an IETF standard that extends the STUN protocol to help diagnose and characterize NAT and firewall behavior for improved NAT traversal.
-
A.
RFC 5080
RFC 5080 is an IETF standards-track document that provides clarifications and implementation guidelines for the Remote Authentication Dial-In User Service (RADIUS) protocol and related extensions.
-
B.
RFC 5890
RFC 5890 is an Internet Engineering Task Force (IETF) standard that defines the terminology and concepts for Internationalized Domain Names (IDNs) in the Domain Name System (DNS).
-
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 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 5620
RFC 5620 is an IETF standards document that defines a framework for managing and monitoring MPLS-based transport networks.
- F. None of above. chosen
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_69e11e2e8ea4819084210fe06d3a1b8d |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f127ccc2ec8190a94d69530d00c06c |
completed | April 28, 2026, 9:34 p.m. |
Created at: April 16, 2026, 8:24 p.m.