Triple
T270784
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC |
E5627
|
entity |
| Predicate | originatedBy |
P1408
|
FINISHED |
| Object |
Network Working Group
The Network Working Group was an early collaborative body of researchers and engineers that developed and documented foundational protocols and standards for the ARPANET, which evolved into today’s Internet.
|
E35271
|
NE FINISHED |
How this triple was built (5 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: Network Working Group | Statement: [RFC, originatedBy, Network Working Group]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Network Working Group Context triple: [RFC, originatedBy, Network Working Group]
-
A.
Internet Engineering Steering Group
The Internet Engineering Steering Group (IESG) is the body within the Internet Engineering Task Force responsible for technical management of IETF activities and the approval and publication of Internet standards.
-
B.
Internet Engineering Task Force
The Internet Engineering Task Force (IETF) is an open, international standards organization that develops and promotes voluntary technical standards, particularly those that make up the core protocols and architecture of the Internet.
-
C.
Internet Architecture Board
The Internet Architecture Board is a committee of the Internet Society that provides architectural oversight, standards guidance, and strategic direction for the development of the Internet.
-
D.
IEEE 802.1 Working Group
The IEEE 802.1 Working Group is a standards body within the IEEE 802 LAN/MAN Standards Committee responsible for developing and maintaining networking standards for bridging, network management, and time-sensitive networking.
-
E.
IETF RTCWEB Working Group
The IETF RTCWEB Working Group is a standards body group within the Internet Engineering Task Force responsible for defining the protocols and architecture that enable real-time communication capabilities in web browsers and applications.
- 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: Network Working Group Triple: [RFC, originatedBy, Network Working Group]
Generated description
The Network Working Group was an early collaborative body of researchers and engineers that developed and documented foundational protocols and standards for the ARPANET, which evolved into today’s Internet.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Network Working Group Target entity description: The Network Working Group was an early collaborative body of researchers and engineers that developed and documented foundational protocols and standards for the ARPANET, which evolved into today’s Internet.
-
A.
Internet Engineering Steering Group
The Internet Engineering Steering Group (IESG) is the body within the Internet Engineering Task Force responsible for technical management of IETF activities and the approval and publication of Internet standards.
-
B.
Internet Engineering Task Force
The Internet Engineering Task Force (IETF) is an open, international standards organization that develops and promotes voluntary technical standards, particularly those that make up the core protocols and architecture of the Internet.
-
C.
Internet Architecture Board
The Internet Architecture Board is a committee of the Internet Society that provides architectural oversight, standards guidance, and strategic direction for the development of the Internet.
-
D.
IEEE 802.1 Working Group
The IEEE 802.1 Working Group is a standards body within the IEEE 802 LAN/MAN Standards Committee responsible for developing and maintaining networking standards for bridging, network management, and time-sensitive networking.
-
E.
IETF RTCWEB Working Group
The IETF RTCWEB Working Group is a standards body group within the Internet Engineering Task Force responsible for defining the protocols and architecture that enable real-time communication capabilities in web browsers and applications.
- F. None of above. chosen
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originatedBy Context triple: [RFC, originatedBy, Network Working Group]
-
A.
initiatedBy
chosen
Indicates that an action, event, or process was started or set in motion by a particular entity.
-
B.
transmittedFrom
Indicates that something (such as information, a signal, or a disease) has been passed or conveyed from one source entity to another.
-
C.
hasOriginIn
Indicates that something begins, arises, or is derived from a specified source, place, or cause.
-
D.
cityOfOriginal
Indicates the city from which something or someone originally comes or was first created or established.
-
E.
formedBy
Indicates that something comes into existence or is created as a result of a specific agent, process, or combination of components.
- F. None of above.
Provenance (6 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_69a25853594c8190b05ec3a586ec88bf |
completed | Feb. 28, 2026, 2:52 a.m. |
| NER | Named-entity recognition | batch_69a25e69a9248190b9e7959b43223baa |
completed | Feb. 28, 2026, 3:18 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a38f51aeac81908c6d398e650dc315 |
completed | March 1, 2026, 12:58 a.m. |
| NEDg | Description generation | batch_69a38fbfac808190b2b551dcbfe6faff |
completed | March 1, 2026, 1 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69a3903779e88190a00c44a522e82022 |
completed | March 1, 2026, 1:02 a.m. |
| PD | Predicate disambiguation | batch_69a25b721180819080d43c43fcbccf87 |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:57 a.m.