Triple
T1768358
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 3418 |
E38815
|
entity |
| Predicate | series |
P1761
|
FINISHED |
| Object |
STD 62
STD 62 is an Internet Standards Track specification that defines part of the Simple Network Management Protocol (SNMP) framework for network management on the Internet.
|
E200055
|
NE FINISHED |
How this triple was built (4 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: STD 62 | Statement: [RFC 3418, series, STD 62]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: STD 62 Context triple: [RFC 3418, series, STD 62]
-
A.
STD 68
STD 68 is an Internet Standard that specifies the core Internet Control Message Protocol (ICMP) used for network diagnostics and error reporting in IP networks.
-
B.
STD 5
STD 5 is the Internet Standard that defines the core Internet Protocol (IP), as specified primarily in RFC 791.
-
C.
STD 1
STD 1 is an early Internet Standard that specifies the foundational Internet Protocol (IP), defining how data packets are addressed and routed across interconnected networks.
-
D.
STD 90
STD 90 is an Internet Standard that specifies the core Internet Protocol (IP) and related requirements fundamental to interoperable networking on the Internet.
-
E.
STD 3
STD 3 is an Internet Standard that specifies the core Internet Protocol (IP) used for addressing and routing packets across interconnected networks.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: STD 62 Triple: [RFC 3418, series, STD 62]
Generated description
STD 62 is an Internet Standards Track specification that defines part of the Simple Network Management Protocol (SNMP) framework for network management on the Internet.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: STD 62 Target entity description: STD 62 is an Internet Standards Track specification that defines part of the Simple Network Management Protocol (SNMP) framework for network management on the Internet.
-
A.
STD 68
STD 68 is an Internet Standard that specifies the core Internet Control Message Protocol (ICMP) used for network diagnostics and error reporting in IP networks.
-
B.
STD 5
STD 5 is the Internet Standard that defines the core Internet Protocol (IP), as specified primarily in RFC 791.
-
C.
STD 1
STD 1 is an early Internet Standard that specifies the foundational Internet Protocol (IP), defining how data packets are addressed and routed across interconnected networks.
-
D.
STD 90
STD 90 is an Internet Standard that specifies the core Internet Protocol (IP) and related requirements fundamental to interoperable networking on the Internet.
-
E.
STD 3
STD 3 is an Internet Standard that specifies the core Internet Protocol (IP) used for addressing and routing packets across interconnected networks.
- F. None of above. chosen
Provenance (5 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_69a8862e61708190af97b9838cc3f5de |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69aa648bb44c81909245fb7ee23cb132 |
completed | March 6, 2026, 5:22 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ada991564c81909ae00fdcb47f52af |
completed | March 8, 2026, 4:53 p.m. |
| NEDg | Description generation | batch_69adab0295b8819092cb51082337b97b |
completed | March 8, 2026, 4:59 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69adaea83bfc8190a526d5f2bd460e4c |
completed | March 8, 2026, 5:15 p.m. |
Created at: March 4, 2026, 7:31 p.m.