Triple
T8367722
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 866 |
E197375
|
entity |
| Predicate | relatedTo |
P37
|
FINISHED |
| Object | RFC 867 |
E198538
|
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 867 | Statement: [RFC 866, relatedTo, RFC 867]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 867 Context triple: [RFC 866, relatedTo, RFC 867]
-
A.
RFC 867
chosen
RFC 867 is an early Internet standard that defines the "Daytime Protocol," a simple service for returning the current date and time over a network connection.
-
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 862
RFC 862 is an Internet standard that specifies the Echo Protocol, a simple service used primarily for testing and measurement by sending data to a server that returns it unchanged.
-
D.
RFC 870
RFC 870 is an early Internet standards document that refines and extends the Telnet protocol specifications originally defined in RFC 854.
-
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_69ca82f56730819080cec5d991c76f4c |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb808e56fc81908b5d37482f29452d |
completed | March 31, 2026, 8:06 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cdc78c0c208190ba590c74512a4043 |
completed | April 2, 2026, 1:34 a.m. |
Created at: March 30, 2026, 6 p.m.