Triple
T10601760
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 1908 |
E275764
|
entity |
| Predicate | updates |
P4061
|
FINISHED |
| Object | RFC 1441 |
E203732
|
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 1441 | Statement: [RFC 1908, updates, RFC 1441]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 1441 Context triple: [RFC 1908, updates, RFC 1441]
-
A.
RFC 1441
chosen
RFC 1441 is an early standards-track document in the Simple Network Management Protocol (SNMP) framework that was later superseded by RFC 1901 as the protocol evolved.
-
B.
RFC 1444
RFC 1444 is an Internet standards document that defines the SNMPv2 MIB for managing SNMP entities in network management systems.
-
C.
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).
-
D.
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.
-
E.
RFC 1541
RFC 1541 is an early Internet standards document that originally specified the Dynamic Host Configuration Protocol (DHCP) for automatic IP address assignment before being superseded by RFC 2131.
- 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_69d6aaf948d88190806cc3a8c47a3fb2 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d6ded61d5c8190b13890c964b59949 |
completed | April 8, 2026, 11:03 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d95ea8f1688190aa36e29b52667d26 |
completed | April 10, 2026, 8:33 p.m. |
Created at: April 8, 2026, 7:31 p.m.