Triple
T10141804
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 1541 |
E231599
|
entity |
| Predicate | obsoletedBy |
P101
|
FINISHED |
| Object | RFC 2131 |
E34938
|
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 2131 | Statement: [RFC 1541, obsoletedBy, RFC 2131]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 2131 Context triple: [RFC 1541, obsoletedBy, RFC 2131]
-
A.
RFC 2131
chosen
RFC 2131 is the Internet Engineering Task Force (IETF) standard that specifies the Dynamic Host Configuration Protocol (DHCP) used for automatic IP address and configuration assignment in IP networks.
-
B.
RFC 2181
RFC 2181 is an Internet standards document that clarifies and updates the Domain Name System (DNS) specifications, particularly regarding DNS data consistency, caching, and authoritative information.
-
C.
RFC 2911
RFC 2911 is the core specification that defines the Internet Printing Protocol (IPP) model, operations, and attributes used for network printing.
-
D.
RFC 2132
RFC 2132 is an Internet Engineering Task Force (IETF) standard that specifies the DHCP options and BOOTP vendor extensions used for configuring network clients.
-
E.
RFC 2571
RFC 2571 was an earlier specification in the Simple Network Management Protocol (SNMP) framework that was later superseded and updated by RFC 3411.
- 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_69ca848364f881908a24366a6feec1db |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cdeb2599e0819090184631e481310c |
completed | April 2, 2026, 4:05 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d2e60e51488190a6097837eb3ce18a |
completed | April 5, 2026, 10:45 p.m. |
Created at: March 30, 2026, 9:07 p.m.