Triple
T21224560
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 1889 |
E523056
|
entity |
| Predicate | obsoletedBy |
P101
|
FINISHED |
| Object | RFC 3550 |
—
|
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 3550 | Statement: [RFC 1889, obsoletedBy, RFC 3550]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 3550 Context triple: [RFC 1889, obsoletedBy, RFC 3550]
-
A.
RFC 3550
chosen
RFC 3550 is the IETF standard that specifies the Real-time Transport Protocol (RTP) for delivering audio and video over IP networks.
-
B.
RFC 3551
RFC 3551 is an IETF standard that specifies the audio and video profile for the Real-time Transport Protocol (RTP), including default payload formats and parameter assignments for real-time multimedia communication.
-
C.
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.
-
D.
RFC 3711
RFC 3711 is the IETF specification that defines the Secure Real-time Transport Protocol (SRTP), a framework for providing encryption, message authentication, and integrity for real-time audio and video over IP networks.
-
E.
RFC 3650
RFC 3650 is an IETF document that specifies the architectural framework and core concepts of the Handle System, a global identifier and resolution system for digital resources.
- 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_69e0b512ad94819087942b2ed925185f |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e734a9c9f88190817b574f916886e5 |
completed | April 21, 2026, 8:26 a.m. |
Created at: April 16, 2026, 3:44 p.m.