Triple
T2751855
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Internet-Drafts |
E61006
|
entity |
| Predicate | isNot |
P4300
|
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: [Internet-Drafts, isNot, RFC]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC Context triple: [Internet-Drafts, isNot, RFC]
-
A.
RFC
RFC is the commonly used abbreviation for Reading Football Club, a professional English football team based in Reading, Berkshire.
-
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 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.
-
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.
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.
- 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_69ab4b7a85bc819094a349b84beb1f2c |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abdb6d08088190b489de15a120ba3f |
completed | March 7, 2026, 8:01 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69afbbd86ac88190a4aba335ef9942e4 |
completed | March 10, 2026, 6:36 a.m. |
Created at: March 6, 2026, 9:56 p.m.