Triple
T7928410
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 8728 |
E184124
|
entity |
| Predicate | partOf |
P40
|
FINISHED |
| Object | RFC Series |
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: RFC Series | Statement: [RFC 8728, partOf, RFC Series]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC Series Context triple: [RFC 8728, partOf, RFC Series]
-
A.
RFC
RFC is the commonly used abbreviation for Reading Football Club, a professional English football team based in Reading, Berkshire.
-
B.
RFC
RFC is the common abbreviation for Rangers Football Club, a professional football team based in Glasgow, Scotland.
-
C.
RFC
RFC is the common abbreviation for the Richmond Football Club, a professional Australian rules football team based in Melbourne that competes in the Australian Football League (AFL).
-
D.
RFC Series Working Group
The RFC Series Working Group is an IETF body responsible for defining policies and processes that govern the publication and evolution of the Request for Comments (RFC) document series.
-
E.
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.
- 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_69ca828fe7bc819090f52c88dcd72183 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3ac9ac4c819082cd2190fc3ce5a2 |
completed | March 31, 2026, 3:08 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cc5643fd3081908fc9a413a7920145 |
completed | March 31, 2026, 11:18 p.m. |
Created at: March 30, 2026, 5:07 p.m.