Triple
T1712344
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IANA Naming Function Contract |
E37209
|
entity |
| Predicate | relatedTo |
P37
|
FINISHED |
| Object | IANA functions contract |
E37209
|
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: IANA functions contract | Statement: [IANA Naming Function Contract, relatedTo, IANA functions contract]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: IANA functions contract Context triple: [IANA Naming Function Contract, relatedTo, IANA functions contract]
-
A.
IANA Naming Function Contract
chosen
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.
IETF Stream
The IETF Stream is the primary publication channel through which the Internet Engineering Task Force issues its technical standards and best current practice documents as RFCs.
-
E.
RFC 4217
RFC 4217 is an Internet standard that specifies how to secure FTP sessions using Transport Layer Security (TLS), commonly known as FTPS.
- 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_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. |
Created at: March 4, 2026, 7:30 p.m.