Triple
T13636484
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 1071 |
E325860
|
entity |
| Predicate | relatedTo |
P37
|
FINISHED |
| Object | RFC 768 |
E121262
|
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 768 | Statement: [RFC 1071, relatedTo, RFC 768]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 768 Context triple: [RFC 1071, relatedTo, RFC 768]
-
A.
RFC 768
chosen
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.
-
B.
RFC 791
RFC 791 is the foundational Internet standard that specifies the design, structure, and operation of the Internet Protocol version 4 (IPv4).
-
C.
RFC 868
RFC 868 is an Internet standard that specifies the Time Protocol, a simple service for transmitting the time over a network.
-
D.
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.
-
E.
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.
- 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_69d8076beddc8190a53156f5bea77f5e |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc5a616dc81908b8c1213e1d4beed |
completed | April 12, 2026, 4:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f78af297008190b12256c936714213 |
completed | May 3, 2026, 5:50 p.m. |
Created at: April 9, 2026, 9:51 p.m.