Triple
T8723044
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 877 |
E207057
|
entity |
| Predicate | series |
P1761
|
FINISHED |
| Object |
STD 37
STD 37 is an Internet Standard that defines a core protocol or specification within the official Internet standards series maintained by the IETF.
|
E752945
|
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 37 | Statement: [RFC 877, series, STD 37]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: STD 37 Context triple: [RFC 877, series, STD 37]
-
A.
STD 17
STD 17 is an Internet Standards Track specification series that defines the core structure and management information base (MIB) for the Simple Network Management Protocol (SNMP).
-
B.
STD 3
STD 3 is an Internet Standard that specifies the core Internet Protocol (IP) used for addressing and routing packets across interconnected 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 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.
-
E.
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.
- 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 37 Triple: [RFC 877, series, STD 37]
Generated description
STD 37 is an Internet Standard that defines a core protocol or specification within the official Internet standards series maintained by the IETF.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: STD 37 Target entity description: STD 37 is an Internet Standard that defines a core protocol or specification within the official Internet standards series maintained by the IETF.
-
A.
STD 17
STD 17 is an Internet Standards Track specification series that defines the core structure and management information base (MIB) for the Simple Network Management Protocol (SNMP).
-
B.
STD 3
STD 3 is an Internet Standard that specifies the core Internet Protocol (IP) used for addressing and routing packets across interconnected 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 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.
-
E.
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.
- 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_69ca835811d8819081ea00fd2a2c9a1c |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5d0791208190b043332247372d7b |
completed | March 31, 2026, 11:47 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cf290001108190a90784b13a0a25b1 |
completed | April 3, 2026, 2:42 a.m. |
| NEDg | Description generation | batch_69cf2bd32cc881909ac8a61befa9929e |
completed | April 3, 2026, 2:54 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69cf2c69f83481909423858668d03a8b |
completed | April 3, 2026, 2:56 a.m. |
Created at: March 30, 2026, 6:36 p.m.