Triple
T10158249
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 4512 |
E233824
|
entity |
| Predicate | obsoletes |
P101
|
FINISHED |
| Object | RFC 3377 |
E845097
|
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 3377 | Statement: [RFC 4512, obsoletes, RFC 3377]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 3377 Context triple: [RFC 4512, obsoletes, RFC 3377]
-
A.
RFC 3377
chosen
RFC 3377 is an Internet Engineering Task Force (IETF) document that previously specified Lightweight Directory Access Protocol (LDAP) version 3 technical details before being superseded by later standards.
-
B.
RFC 3207
RFC 3207 is the Internet standard that specifies the STARTTLS extension for upgrading plain text email connections to use TLS encryption in SMTP.
-
C.
RFC 3977
RFC 3977 is the Internet standard that defines the Network News Transfer Protocol (NNTP), updating and replacing the earlier specification in RFC 977.
-
D.
RFC 3727
RFC 3727 is an Internet Engineering Task Force (IETF) document that defined earlier specifications for LDAP-related schema or matching rules, later superseded by RFC 4517.
-
E.
RFC 3710
RFC 3710 is an IETF document that defines the purpose, structure, and procedures of the Internet Engineering Steering Group (IESG) within the Internet standards process.
- 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_69ca848e80748190b91d1e04d35512c7 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cdec5507f08190b47f797bacd5640c |
completed | April 2, 2026, 4:11 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d354fc0a808190aa57b68708d91590 |
completed | April 6, 2026, 6:38 a.m. |
Created at: March 30, 2026, 9:09 p.m.