Triple
T21091481
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Robustness principle |
E519647
|
entity |
| Predicate | mentionedIn |
P831
|
FINISHED |
| Object | RFC 1122 |
—
|
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 1122 | Statement: [Robustness principle, mentionedIn, RFC 1122]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 1122 Context triple: [Robustness principle, mentionedIn, RFC 1122]
-
A.
RFC 1122
chosen
RFC 1122 is an Internet standard that defines host-level requirements and core behaviors for Internet protocol implementations, including TCP/IP.
-
B.
RFC 1119
RFC 1119 is an early specification in the Network Time Protocol (NTP) series that was later superseded by RFC 1305.
-
C.
RFC 1700
RFC 1700 is an Internet standards document that served as the central Assigned Numbers registry, cataloging protocol parameters such as port numbers, protocol numbers, and other key Internet identifiers.
-
D.
RFC 1812
RFC 1812 is an Internet standards document that defines the requirements and behavior for IPv4 routers in the Internet protocol suite.
-
E.
RFC 1662
RFC 1662 is an Internet Engineering Task Force (IETF) standard that specifies the framing for Point-to-Point Protocol (PPP) over synchronous and asynchronous serial links.
- 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.