Triple
T3054551
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 950 |
E60448
|
entity |
| Predicate | relatedTo |
P37
|
FINISHED |
| Object | RFC 791 |
E9801
|
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 791 | Statement: [RFC 950, relatedTo, RFC 791]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 791 Context triple: [RFC 950, relatedTo, RFC 791]
-
A.
RFC 791
chosen
RFC 791 is the foundational Internet standard that specifies the design, structure, and operation of the Internet Protocol version 4 (IPv4).
-
B.
RFC 792
RFC 792 is the Internet standard document that specifies the Internet Control Message Protocol (ICMP), which is used for network diagnostics and error reporting in IP networks.
-
C.
RFC 793
RFC 793 is the foundational Internet standard that defines the Transmission Control Protocol (TCP), specifying how reliable, ordered, and error-checked data transmission works between hosts on an IP network.
-
D.
RFC 1449
RFC 1449 is an early Internet standards document that specified a version of the Simple Network Management Protocol (SNMP) used for managing devices on IP networks.
-
E.
RFC 974
RFC 974 is an early Internet standard that defined the original mechanisms for mail routing and the use of MX records in the Domain Name System (DNS).
- 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_69ad8578137c81908259dcb27c7d6d7c |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ad9bf6b9948190bc957bfd1579c471 |
completed | March 8, 2026, 3:55 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b1ef03425c8190a44486ab563c210f |
completed | March 11, 2026, 10:38 p.m. |
Created at: March 8, 2026, 3:02 p.m.