Triple
T22027973
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Session Description Protocol |
E544013
|
entity |
| Predicate | definedInRFC |
P5655
|
FINISHED |
| Object | RFC 4566 |
—
|
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 4566 | Statement: [Session Description Protocol, definedInRFC, RFC 4566]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 4566 Context triple: [Session Description Protocol, definedInRFC, RFC 4566]
-
A.
RFC 4566
chosen
RFC 4566 is the Internet standards document that specifies the Session Description Protocol (SDP) used to describe multimedia communication sessions for purposes such as session announcement, invitation, and parameter negotiation.
-
B.
RFC 5766
RFC 5766 is an IETF specification that defines the Traversal Using Relays around NAT (TURN) protocol for relaying network traffic to help clients communicate across NATs and firewalls.
-
C.
RFC 3550
RFC 3550 is the IETF standard that specifies the Real-time Transport Protocol (RTP) for delivering audio and video over IP networks.
-
D.
RFC 2732
RFC 2732 is an Internet standards document that specified the use of bracketed IPv6 addresses in URLs before being superseded by RFC 3986.
-
E.
RFC 2445
RFC 2445 is the Internet standards document that defines the iCalendar format for representing and exchanging calendaring and scheduling information.
- 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_69f127cdf5c08190ac804664d6e56fe2 |
completed | April 28, 2026, 9:34 p.m. |
Created at: April 16, 2026, 8:24 p.m.