Triple
T8891330
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 1 |
E211681
|
entity |
| Predicate | hasAbbreviation |
P43
|
FINISHED |
| Object | RFC 1 |
E211681
|
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 1 | Statement: [RFC 1, hasAbbreviation, RFC 1]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 1 Context triple: [RFC 1, hasAbbreviation, RFC 1]
-
A.
RFC 1
chosen
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.
-
B.
RFC 9001
RFC 9001 is an IETF standard that specifies how the TLS 1.3 protocol is used to secure QUIC connections, defining the cryptographic handshake and key management for QUIC.
-
C.
RFC 1010
RFC 1010 was an early Internet standards document that provided an official list of assigned protocol numbers and related parameters before being superseded by later updates.
-
D.
RFC 1700
RFC 1700 is an Internet standards document that served as the central Assigned Numbers registry, cataloging protocol parameters such as port numbers, protocol numbers, and other key Internet identifiers.
-
E.
RFC 1031
RFC 1031 is an early Internet standards document that specified guidelines for the implementation and operation of certain TCP/IP networking protocols before being superseded by later updates.
- 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_69ca83907954819096d52a245b635841 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc61ba33c48190a657fc4147a326c0 |
completed | April 1, 2026, 12:07 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cfabf01d048190bed52b5b001d7ffa |
completed | April 3, 2026, noon |
Created at: March 30, 2026, 6:54 p.m.