Triple
T2346155
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 1350 |
E45135
|
entity |
| Predicate | obsoletes |
P101
|
FINISHED |
| Object | RFC 783 |
E45563
|
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 783 | Statement: [RFC 1350, obsoletes, RFC 783]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 783 Context triple: [RFC 1350, obsoletes, RFC 783]
-
A.
RFC 783
chosen
RFC 783 is the original specification that defines the Trivial File Transfer Protocol (TFTP), a simple protocol for transferring files over a network.
-
B.
RFC 877
RFC 877 is an early Internet standards document that specifies the standard for Internet Control Message Protocol (ICMP) echo messages used for network diagnostics such as the "ping" utility.
-
C.
RFC 870
RFC 870 is an early Internet standards document that refines and extends the Telnet protocol specifications originally defined in RFC 854.
-
D.
RFC 973
RFC 973 is an early Internet standards document that refines and extends the domain name system concepts introduced in RFC 882.
-
E.
RFC 857
RFC 857 is an Internet standard that defines the Telnet protocol option for echoing characters, specifying how user input is echoed back in Telnet sessions.
- 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_69a88917935081909b755dbf38e81024 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abc6c9396081908abb2b0a229bb046 |
completed | March 7, 2026, 6:33 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ae9628059481909c96a7661bc87a73 |
completed | March 9, 2026, 9:43 a.m. |
Created at: March 4, 2026, 7:52 p.m.