Triple
T22334488
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 5302 |
E552106
|
entity |
| Predicate | maintainedBy |
P86
|
FINISHED |
| Object | IETF OSPF Working Group |
—
|
NE NERFINISHED |
How this triple was built (3 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: IETF OSPF Working Group | Statement: [RFC 5302, maintainedBy, IETF OSPF Working Group]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: IETF OSPF Working Group Context triple: [RFC 5302, maintainedBy, IETF OSPF Working Group]
-
A.
IETF OPSAWG Working Group
The IETF OPSAWG Working Group is a standards body group within the Internet Engineering Task Force focused on developing and maintaining operational and management practices, guidelines, and related technologies for managing IP networks and services.
-
B.
Support of Address Families in OSPFv3
"Support of Address Families in OSPFv3" is an IETF specification (RFC 5838) that extends OSPFv3 to carry and route multiple address families, such as IPv4 and IPv6, within a single OSPFv3 instance.
-
C.
IETF IPsec Working Group
The IETF IPsec Working Group is a standards body within the Internet Engineering Task Force responsible for developing and maintaining the IP Security (IPsec) protocol suite used to secure Internet communications at the network layer.
-
D.
OSPF
OSPF (Open Shortest Path First) is a widely used interior gateway routing protocol that employs link-state information to determine the most efficient path for data within an IP network.
-
E.
OSPFv3
OSPFv3 is the version of the Open Shortest Path First routing protocol designed to operate over IPv6 networks, providing link-state routing and support for IPv6 addressing and features.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: IETF OSPF Working Group Target entity description: The IETF OSPF Working Group is a standards body within the Internet Engineering Task Force responsible for developing and maintaining the Open Shortest Path First (OSPF) routing protocol specifications.
-
A.
IETF OPSAWG Working Group
The IETF OPSAWG Working Group is a standards body group within the Internet Engineering Task Force focused on developing and maintaining operational and management practices, guidelines, and related technologies for managing IP networks and services.
-
B.
Support of Address Families in OSPFv3
"Support of Address Families in OSPFv3" is an IETF specification (RFC 5838) that extends OSPFv3 to carry and route multiple address families, such as IPv4 and IPv6, within a single OSPFv3 instance.
-
C.
IETF IPsec Working Group
The IETF IPsec Working Group is a standards body within the Internet Engineering Task Force responsible for developing and maintaining the IP Security (IPsec) protocol suite used to secure Internet communications at the network layer.
-
D.
OSPF
OSPF (Open Shortest Path First) is a widely used interior gateway routing protocol that employs link-state information to determine the most efficient path for data within an IP network.
-
E.
OSPFv3
OSPFv3 is the version of the Open Shortest Path First routing protocol designed to operate over IPv6 networks, providing link-state routing and support for IPv6 addressing and features.
- F. None of above. chosen
Provenance (2 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_69e11e482f788190b78d1588fc26d606 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f1577e35f48190b11789d80182653e |
completed | April 29, 2026, 12:57 a.m. |
Created at: April 16, 2026, 8:43 p.m.