Triple
T2260269
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 9002 |
E50020
|
entity |
| Predicate | series |
P1761
|
FINISHED |
| Object | Request for Comments |
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: Request for Comments | Statement: [RFC 9002, series, Request for Comments]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Request for Comments Context triple: [RFC 9002, series, Request for Comments]
-
A.
Global RfCs
Global RfCs are Meta-Wiki-hosted community discussions where Wikimedia contributors from all projects and languages can propose and seek consensus on issues with global or cross-wiki impact.
-
B.
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.
-
C.
RFC
RFC is the commonly used abbreviation for Reading Football Club, a professional English football team based in Reading, Berkshire.
-
D.
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.
-
E.
Internet-Drafts
Internet-Drafts are working documents of the Internet Engineering Task Force (IETF) and its research and architecture bodies that propose, discuss, and refine technical specifications and protocols before they may become Internet standards.
- 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_69a88b01e0048190ba96431b5f990ba9 |
completed | March 4, 2026, 7:41 p.m. |
| NER | Named-entity recognition | batch_69abc15be1288190a55c12674f4a5e03 |
completed | March 7, 2026, 6:10 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ae71cb1540819093db7f91ae66c19f |
completed | March 9, 2026, 7:07 a.m. |
Created at: March 4, 2026, 7:48 p.m.