Triple
T22027169
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IETF BEHAVE working group |
E543996
|
entity |
| Predicate | produced |
P490
|
FINISHED |
| Object | RFC 6146 |
—
|
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 6146 | Statement: [IETF BEHAVE working group, produced, RFC 6146]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 6146 Context triple: [IETF BEHAVE working group, produced, RFC 6146]
-
A.
RFC 6146
chosen
RFC 6146 is an IETF standard that specifies the behavior and requirements for NAT64, enabling IPv6-only clients to communicate with IPv4 servers through protocol translation.
-
B.
RFC 5046
RFC 5046 is an IETF standard that defines the marker PDU aligned framing (MPA) protocol used to support RDMA over TCP/IP in the iWARP architecture.
-
C.
RFC 5546
RFC 5546 is an Internet standards document that specifies the iCalendar Transport-Independent Interoperability Protocol (iTIP) for exchanging calendaring and scheduling information.
-
D.
RFC 6066
RFC 6066 is an Internet Engineering Task Force (IETF) standard that specifies Transport Layer Security (TLS) extensions, including the widely used Server Name Indication (SNI) extension.
-
E.
RFC 6186
RFC 6186 is an Internet Engineering Task Force (IETF) standard that originally specified how to use DNS SRV records to locate email submission and access services for a given domain.
- 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.