Triple
T21091480
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Robustness principle |
E519647
|
entity |
| Predicate | mentionedIn |
P831
|
FINISHED |
| Object | RFC 761 |
—
|
NE NERFINISHED |
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 761 | Statement: [Robustness principle, mentionedIn, RFC 761]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 761 Context triple: [Robustness principle, mentionedIn, RFC 761]
-
A.
RFC 761
chosen
RFC 761 is an early Internet standard document that specifies the Transmission Control Protocol (TCP), within which Postel’s law was famously articulated.
-
B.
RFC 765
RFC 765 was an early specification of the File Transfer Protocol (FTP) that defined how files are transferred over TCP/IP networks before being superseded by later standards.
-
C.
RFC 760
RFC 760 is an early Internet standard document authored by Jon Postel that specifies the original Internet Protocol (IP).
-
D.
RFC 1661
RFC 1661 is the original specification of the Point-to-Point Protocol (PPP), defining a standard method for transporting multi-protocol datagrams over point-to-point links.
-
E.
RFC 1771
RFC 1771 is an early specification of the Border Gateway Protocol (BGP-4) used for inter-domain routing on the Internet, later superseded by RFC 4271.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0b507dd9081908fb8bfcbef4c8b46 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7094f6ebc8190a90b014755a9d4a6 |
completed | April 21, 2026, 5:21 a.m. |
Created at: April 16, 2026, 2:51 p.m.