Triple
T8258032
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 3417 |
E193118
|
entity |
| Predicate | publishedIn |
P309
|
FINISHED |
| Object | STD 62 |
E200055
|
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: STD 62 | Statement: [RFC 3417, publishedIn, STD 62]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: STD 62 Context triple: [RFC 3417, publishedIn, STD 62]
-
A.
STD 62
chosen
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.
-
B.
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.
-
C.
STD 5
STD 5 is the Internet Standard that defines the core Internet Protocol (IP), as specified primarily in RFC 791.
-
D.
STD 7
STD 7 is an Internet Standards Track specification in the IETF standards series, corresponding to RFC 2131, which defines the Dynamic Host Configuration Protocol (DHCP) for automated IP address assignment and configuration.
-
E.
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.
- 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_69ca82dfad9c8190b8cd18fb89f50f40 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb78fce9308190ac36512e80b06b52 |
completed | March 31, 2026, 7:34 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cd355bef508190894bd01ec39e83f6 |
completed | April 1, 2026, 3:10 p.m. |
Created at: March 30, 2026, 5:49 p.m.