Triple
T23313075
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 5061 |
E590632
|
entity |
| Predicate | extends |
P1244
|
FINISHED |
| Object | RFC 2960 |
—
|
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 2960 | Statement: [RFC 5061, extends, RFC 2960]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 2960 Context triple: [RFC 5061, extends, RFC 2960]
-
A.
RFC 2960
chosen
RFC 2960 is the original specification that defined the Stream Control Transmission Protocol (SCTP), a transport-layer protocol designed for message-oriented, multi-stream communication.
-
B.
RFC 4960
RFC 4960 is the IETF standards document that specifies the Stream Control Transmission Protocol (SCTP), a transport-layer protocol designed for message-oriented, multi-stream, and multi-homed communication.
-
C.
RFC 2910
RFC 2910 is an IETF specification that defines the Internet Printing Protocol/1.1 model and encoding for network printing.
-
D.
RFC 5340
RFC 5340 is the IETF specification that defines OSPF version 3, the link-state routing protocol for IPv6 networks.
-
E.
RFC 2760
RFC 2760 is an Internet Engineering Task Force (IETF) document that provided guidelines and considerations for the deployment and operation of Classless Inter-Domain Routing (CIDR) on the Internet.
- 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_69e25d1d32188190948eb76909d1dcc3 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1972ca70481909e2415c65964210a |
completed | April 29, 2026, 5:29 a.m. |
Created at: April 17, 2026, 5:06 p.m.