Triple
T8113420
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 4035 |
E189410
|
entity |
| Predicate | obsoletes |
P101
|
FINISHED |
| Object | RFC 2535 |
E707271
|
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 2535 | Statement: [RFC 4035, obsoletes, RFC 2535]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 2535 Context triple: [RFC 4035, obsoletes, RFC 2535]
-
A.
RFC 2535
chosen
RFC 2535 is an earlier DNS Security Extensions (DNSSEC) specification that was later superseded by updated standards such as RFC 4033.
-
B.
RFC 2575
RFC 2575 is an earlier IETF standard that defined the View-based Access Control Model (VACM) for SNMP before being superseded by RFC 3415.
-
C.
RFC 4515
RFC 4515 is an Internet standard that specifies the string representation of LDAP search filters used in directory service queries.
-
D.
RFC 2595
RFC 2595 is an Internet standard that originally defined the use of TLS to secure email-related protocols such as IMAP, POP3, and ACAP.
-
E.
RFC 1055
RFC 1055 is an early Internet standard that specifies the Serial Line Internet Protocol (SLIP) for transmitting IP packets over serial connections.
- 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_69ca82baad008190ab2859712b9b1607 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb432d7dfc8190b9c980f32c7b4623 |
completed | March 31, 2026, 3:44 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cc9433a5848190aac09a2589061b53 |
completed | April 1, 2026, 3:42 a.m. |
Created at: March 30, 2026, 5:32 p.m.