Triple
T10069122
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 2060 |
E213172
|
entity |
| Predicate | series |
P1761
|
FINISHED |
| Object | RFC |
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 | Statement: [RFC 2060, series, RFC]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC Context triple: [RFC 2060, series, RFC]
-
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 the Richmond Football Club, a professional Australian rules football team based in Melbourne that competes in the Australian Football League (AFL).
-
C.
RFC
RFC is the common abbreviation for Rangers Football Club, a professional football team based in Glasgow, Scotland.
-
D.
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.
-
E.
RFC 1
RFC 1 is the first Request for Comments document, published in 1969, which laid the groundwork for the development of the ARPANET and the modern Internet protocol standards process.
- 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_69ca83977128819084084eb7d1d8c52a |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cdcff8d9c08190bc030f1dcc696310 |
completed | April 2, 2026, 2:10 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d29a96fc888190aec7cd364a0d7fb1 |
completed | April 5, 2026, 5:23 p.m. |
Created at: March 30, 2026, 8:58 p.m.