Triple
T8407612
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 867 |
E198538
|
entity |
| Predicate | relatedTo |
P37
|
FINISHED |
| Object | RFC 868 |
E184121
|
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 868 | Statement: [RFC 867, relatedTo, RFC 868]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 868 Context triple: [RFC 867, relatedTo, RFC 868]
-
A.
RFC 868
chosen
RFC 868 is an Internet standard that specifies the Time Protocol, a simple service for transmitting the time over a network.
-
B.
RFC 867
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.
-
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 768
RFC 768 is the Internet standard that defines the User Datagram Protocol (UDP), a core transport-layer protocol used for low-latency, connectionless data transmission.
-
E.
RFC 883
RFC 883 was an early Internet standard that originally specified the Domain Name System (DNS) before being superseded by later DNS specifications.
- 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_69ca8310df9c8190b25f16161cca3e41 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cb831409308190981089c303ebaef4 |
completed | March 31, 2026, 8:17 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ce03035e148190867b60ddaeb8d761 |
completed | April 2, 2026, 5:47 a.m. |
Created at: March 30, 2026, 6:05 p.m.