Triple
T13636376
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 1010 |
E325858
|
entity |
| Predicate | obsoletedBy |
P101
|
FINISHED |
| Object | RFC 3232 |
E741736
|
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 3232 | Statement: [RFC 1010, obsoletedBy, RFC 3232]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 3232 Context triple: [RFC 1010, obsoletedBy, RFC 3232]
-
A.
RFC 3232
chosen
RFC 3232 is an IETF document that provides the current list of assigned Internet protocol numbers and related parameters, updating and replacing earlier registries.
-
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 3652
RFC 3652 is an IETF standards-track document that specifies the technical architecture and protocols of the Handle System for assigning, managing, and resolving persistent digital identifiers.
-
D.
RFC 3410
RFC 3410 is an informational RFC that provides an overview, framework, and goals for the Simple Network Management Protocol version 3 (SNMPv3) and its related specifications.
-
E.
RFC 3205
RFC 3205 is an informational Internet standard that provides guidelines and considerations for designing and deploying application protocols that use HTTP as a substrate.
- 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.