Triple
T13636374
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 1010 |
E325858
|
entity |
| Predicate | obsoletedBy |
P101
|
FINISHED |
| Object | RFC 1340 |
E1048474
|
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 1340 | Statement: [RFC 1010, obsoletedBy, RFC 1340]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 1340 Context triple: [RFC 1010, obsoletedBy, RFC 1340]
-
A.
RFC 1340
chosen
RFC 1340 is an Internet Engineering Task Force (IETF) document that historically defined the official list of Internet protocol numbers and related assignments.
-
B.
RFC 1350
RFC 1350 is the Internet standards document that defines the Trivial File Transfer Protocol (TFTP), a simple protocol for transferring files over a network.
-
C.
RFC 1442
RFC 1442 is an early Internet standards document that defined the Structure of Management Information (SMI) for version 2 of the Simple Network Management Protocol (SNMPv2).
-
D.
RFC 1310
RFC 1310 was an early document in the Internet standards process that outlined procedures and guidelines for developing and standardizing Internet protocols before being superseded by RFC 2026.
-
E.
RFC 1331
RFC 1331 is an early specification in the Point-to-Point Protocol (PPP) standards series that was later superseded by RFC 1661.
- 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_69d8076beddc8190a53156f5bea77f5e |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc5a616dc81908b8c1213e1d4beed |
completed | April 12, 2026, 4:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f78af297008190b12256c936714213 |
completed | May 3, 2026, 5:50 p.m. |
Created at: April 9, 2026, 9:51 p.m.