Triple
T8852441
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 951 |
E210668
|
entity |
| Predicate | relatedTo |
P37
|
FINISHED |
| Object | RFC 1542 |
E764046
|
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 1542 | Statement: [RFC 951, relatedTo, RFC 1542]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 1542 Context triple: [RFC 951, relatedTo, RFC 1542]
-
A.
RFC 1542
chosen
RFC 1542 is an Internet standards document that updates and clarifies the behavior of BOOTP relay agents and related mechanisms for IP networks.
-
B.
RFC 1642
RFC 1642 is an Internet standards document that defines the UTF-7 encoding for representing Unicode characters in environments restricted to 7-bit data.
-
C.
RFC 1452
RFC 1452 is an early Internet standards document that was later superseded by RFC 1901 as part of the evolution of network protocols.
-
D.
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.
-
E.
RFC 1652
RFC 1652 is an early Internet standards document that defines the 8BITMIME extension for SMTP, enabling the transfer of 8-bit character data in email.
- 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_69ca838a424c8190b1ecac115c2927e7 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc60c3c5548190926e374bbe592180 |
completed | April 1, 2026, 12:03 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cfba0d0c208190923e68e9c64efad6 |
completed | April 3, 2026, 1:01 p.m. |
Created at: March 30, 2026, 6:49 p.m.