Triple
T13636537
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Network interface layer |
E325861
|
entity |
| Predicate | standardizedIn |
P7508
|
FINISHED |
| Object | RFC 1123 |
E184138
|
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 1123 | Statement: [Network interface layer, standardizedIn, RFC 1123]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 1123 Context triple: [Network interface layer, standardizedIn, RFC 1123]
-
A.
RFC 1123
chosen
RFC 1123 is an Internet standards document that refines and extends the requirements for host software, including DNS and related protocols, to ensure interoperability on the early Internet.
-
B.
RFC 923
RFC 923 is an Internet standards document that superseded RFC 870 by updating and refining specifications related to early Internet protocol operations.
-
C.
RFC 5322
RFC 5322 is the Internet standard that defines the syntax and format of text-based email messages, including headers such as From, To, Subject, and Date.
-
D.
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.
-
E.
RFC 1331
RFC 1331 is an early specification in the Point-to-Point Protocol (PPP) standards series that was later superseded by RFC 1661.
- 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_69f79d44e2148190a279aa6d103bf204 |
completed | May 3, 2026, 7:08 p.m. |
Created at: April 9, 2026, 9:51 p.m.