Triple
T1712348
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IANA Naming Function Contract |
E37209
|
entity |
| Predicate | excludes |
P3119
|
FINISHED |
| Object |
IANA protocol parameter functions
IANA protocol parameter functions are the set of administrative and coordination tasks that manage and maintain the unique protocol parameter registries used by Internet standards and protocols.
|
E59889
|
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: IANA protocol parameter functions | Statement: [IANA Naming Function Contract, excludes, IANA protocol parameter functions]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: IANA protocol parameter functions Context triple: [IANA Naming Function Contract, excludes, IANA protocol parameter functions]
-
A.
IANA Naming Function Contract
The IANA Naming Function Contract is the formal agreement that defined how the Internet Assigned Numbers Authority’s naming functions—such as management of the DNS root zone—were performed under oversight prior to the IANA stewardship transition.
-
B.
IANA
IANA (Internet Assigned Numbers Authority) is the global organization responsible for coordinating key elements of the Internet’s infrastructure, including IP address allocation, DNS root zone management, and protocol parameter assignments.
-
C.
BCP 14
BCP 14 is an IETF Best Current Practice document that standardizes the use of requirement-level keywords like “MUST,” “SHOULD,” and “MAY” in technical specifications.
-
D.
RFC 9002
RFC 9002 is an IETF standard that specifies the loss detection and congestion control mechanisms for the QUIC transport protocol.
-
E.
RFC 3207
RFC 3207 is the Internet standard that specifies the STARTTLS extension for upgrading plain text email connections to use TLS encryption in SMTP.
- 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: IANA protocol parameter functions Triple: [IANA Naming Function Contract, excludes, IANA protocol parameter functions]
Generated description
IANA protocol parameter functions are the set of administrative and coordination tasks that manage and maintain the unique protocol parameter registries used by Internet standards and protocols.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: IANA protocol parameter functions Target entity description: IANA protocol parameter functions are the set of administrative and coordination tasks that manage and maintain the unique protocol parameter registries used by Internet standards and protocols.
-
A.
IANA Naming Function Contract
The IANA Naming Function Contract is the formal agreement that defined how the Internet Assigned Numbers Authority’s naming functions—such as management of the DNS root zone—were performed under oversight prior to the IANA stewardship transition.
-
B.
IANA
chosen
IANA (Internet Assigned Numbers Authority) is the global organization responsible for coordinating key elements of the Internet’s infrastructure, including IP address allocation, DNS root zone management, and protocol parameter assignments.
-
C.
BCP 14
BCP 14 is an IETF Best Current Practice document that standardizes the use of requirement-level keywords like “MUST,” “SHOULD,” and “MAY” in technical specifications.
-
D.
RFC 9002
RFC 9002 is an IETF standard that specifies the loss detection and congestion control mechanisms for the QUIC transport protocol.
-
E.
RFC 3207
RFC 3207 is the Internet standard that specifies the STARTTLS extension for upgrading plain text email connections to use TLS encryption in SMTP.
- F. None of above.
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_69a8861912dc8190931af43b4b9158a7 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aa6315afdc81908409435bb47e8ee0 |
completed | March 6, 2026, 5:16 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ad8addf4a48190b19cdb861db5eecd |
completed | March 8, 2026, 2:42 p.m. |
| NEDg | Description generation | batch_69ad957adf1c8190b7c8656c1984f998 |
completed | March 8, 2026, 3:27 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69ad97af6b388190b2af293599108df3 |
completed | March 8, 2026, 3:37 p.m. |
Created at: March 4, 2026, 7:30 p.m.