Triple
T10416825
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 1659 |
E245538
|
entity |
| Predicate | obsoletedBy |
P101
|
FINISHED |
| Object | RFC 2358 |
E823481
|
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 2358 | Statement: [RFC 1659, obsoletedBy, RFC 2358]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 2358 Context triple: [RFC 1659, obsoletedBy, RFC 2358]
-
A.
RFC 2358
chosen
RFC 2358 is an Internet Engineering Task Force (IETF) standards-track document that updates and replaces earlier specifications related to the Point-to-Point Protocol (PPP) and its associated network control protocols.
-
B.
RFC 1908
RFC 1908 is an older Internet standards document related to network management that was later superseded by RFC 3410.
-
C.
RFC 2870
RFC 2870 is an Internet Engineering Task Force (IETF) document that specifies operational and technical requirements for the DNS root name server system.
-
D.
RFC 2845
RFC 2845 is the Internet standard that specifies the Transaction SIGnature (TSIG) mechanism for securing DNS transactions using shared secret keys and message authentication codes.
-
E.
RFC 858
RFC 858 is an early Internet standard that defines the Telnet protocol’s status option, specifying how a Telnet client and server can exchange information about their current status.
- 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_69d381be340c8190b05998703d42d224 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4ea1194e08190a18c3b3002147493 |
completed | April 7, 2026, 11:27 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d7fc0dd480819082edcc49a245ad4f |
completed | April 9, 2026, 7:20 p.m. |
Created at: April 6, 2026, 12:10 p.m.