Triple
T9437955
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 1448 |
E227563
|
entity |
| Predicate | relatedTo |
P37
|
FINISHED |
| Object | RFC 1444 |
E754261
|
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 1444 | Statement: [RFC 1448, relatedTo, RFC 1444]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 1444 Context triple: [RFC 1448, relatedTo, RFC 1444]
-
A.
RFC 1444
chosen
RFC 1444 is an Internet standards document that defines the SNMPv2 MIB for managing SNMP entities in network management systems.
-
B.
RFC 1443
RFC 1443 is an early Internet standards document that specified mechanisms for mapping between X.400 and RFC 822 email addressing and message formats.
-
C.
RFC 2144
RFC 2144 is an Internet standards document that specifies the CAST-128 (CAST5) symmetric-key block cipher for use in cryptographic applications.
-
D.
RFC 1448
RFC 1448 is an early Internet standards document that specified a version of the Simple Network Management Protocol (SNMP) before being superseded by later revisions such as RFC 1905.
-
E.
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).
- 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_69ca8437a7ac81908651de48f2d2141d |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd7edff5e881909b72976e8909ba4b |
completed | April 1, 2026, 8:24 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d1225345488190a1fee54f6feb321d |
completed | April 4, 2026, 2:38 p.m. |
Created at: March 30, 2026, 7:50 p.m.