Triple
T10601766
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 1908 |
E275764
|
entity |
| Predicate | updates |
P4061
|
FINISHED |
| Object | RFC 1452 |
E222149
|
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 1452 | Statement: [RFC 1908, updates, RFC 1452]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 1452 Context triple: [RFC 1908, updates, RFC 1452]
-
A.
RFC 1452
chosen
RFC 1452 is an early Internet standards document that was later superseded by RFC 1901 as part of the evolution of network protocols.
-
B.
RFC 1542
RFC 1542 is an Internet standards document that updates and clarifies the behavior of BOOTP relay agents and related mechanisms for IP networks.
-
C.
RFC 1497
RFC 1497 is an early Internet standards document that defined vendor-specific extensions for the BOOTP protocol, laying groundwork later incorporated into DHCP.
-
D.
RFC 1450
RFC 1450 is an early Internet standards document related to network management that was later superseded by RFC 1901.
-
E.
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.
- 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_69d97a23e24881909afb009baa0ef662 |
completed | April 10, 2026, 10:31 p.m. |
Created at: April 8, 2026, 7:31 p.m.