Triple
T22027164
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IETF BEHAVE working group |
E543996
|
entity |
| Predicate | produced |
P490
|
FINISHED |
| Object | RFC 5382 |
—
|
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: RFC 5382 | Statement: [IETF BEHAVE working group, produced, RFC 5382]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 5382 Context triple: [IETF BEHAVE working group, produced, RFC 5382]
-
A.
RFC 5382
chosen
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.
-
B.
RFC 5302
RFC 5302 is an Internet Engineering Task Force (IETF) document that specified an earlier version of the IPv6 routing protocol for the Open Shortest Path First (OSPF) routing framework before being superseded by RFC 5308.
-
C.
RFC 5892
RFC 5892 is an IETF standard that defines the rules for allowable Unicode code points in Internationalized Domain Names (IDNs) under the IDNA2008 framework.
-
D.
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.
-
E.
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.
- 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_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.