Triple
T487668
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Internet Architecture Board |
E9915
|
entity |
| Predicate | publishes |
P80
|
FINISHED |
| Object | RFCs |
E5627
|
NE FINISHED |
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: RFCs | Statement: [Internet Architecture Board, publishes, RFCs]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFCs Context triple: [Internet Architecture Board, publishes, RFCs]
-
A.
RFCs
chosen
RFCs (Requests for Comments) are a series of technical and organizational documents that define and standardize protocols, procedures, and policies for the Internet and related networks.
-
B.
RFC 1939
RFC 1939 is the Internet standard document that specifies the Post Office Protocol version 3 (POP3) used for retrieving email from a mail server.
-
C.
RFC Editor
The RFC Editor is the organization responsible for editing, publishing, and maintaining the Request for Comments (RFC) series that documents standards and technical notes for the Internet community.
-
D.
RFC 9000
RFC 9000 is the IETF standards document that specifies the QUIC transport protocol, defining its core mechanisms for secure, multiplexed, low-latency communication over UDP.
-
E.
RFC 1906
RFC 1906 is an Internet standard that specifies the transport mappings for SNMPv2, detailing how SNMP messages are carried over various network protocols.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (3 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_69a2e802e2908190ab17c9479e0b6412 |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2f0de66308190a18503a482881cfc |
completed | Feb. 28, 2026, 1:42 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a47471e5ac8190acfed4803183f11a |
completed | March 1, 2026, 5:16 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.