Triple
T8421832
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 1519 |
E198873
|
entity |
| Predicate | obsoletedBy |
P101
|
FINISHED |
| Object | RFC 4632 |
E538268
|
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 4632 | Statement: [RFC 1519, obsoletedBy, RFC 4632]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 4632 Context triple: [RFC 1519, obsoletedBy, RFC 4632]
-
A.
RFC 4632
chosen
RFC 4632 is an Internet standards document that specifies the operational and technical details of Classless Inter-Domain Routing (CIDR) for efficient IP address allocation and routing on the Internet.
-
B.
RFC 4291
RFC 4291 is the core Internet standard that defines the IPv6 addressing architecture, including address formats, allocation, and representation.
-
C.
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.
-
D.
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.
-
E.
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.
- 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_69ca8312d63c8190bf133b676b44a385 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cb859e22f88190a61e7dd6537644b0 |
completed | March 31, 2026, 8:28 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ce035279f48190861b97167fa3882c |
completed | April 2, 2026, 5:49 a.m. |
Created at: March 30, 2026, 6:06 p.m.