Triple
T22815305
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IETF mailing lists |
E565080
|
entity |
| Predicate | governedBy |
P46
|
FINISHED |
| Object | IETF code of conduct |
—
|
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 code of conduct | Statement: [IETF mailing lists, governedBy, IETF code of conduct]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: IETF code of conduct Context triple: [IETF mailing lists, governedBy, IETF code of conduct]
-
A.
IETF governance
IETF governance refers to the structures, processes, and decision-making practices that guide how the Internet Engineering Task Force develops, maintains, and evolves open internet standards.
-
B.
IETF community
The IETF community is the global, open network of engineers, researchers, and other stakeholders who collaboratively develop and maintain Internet standards and related technical documents.
-
C.
IETF BEHAVE working group
The IETF BEHAVE working group was a standards body group within the Internet Engineering Task Force focused on defining and improving how Network Address Translators (NATs) interact with Internet protocols and applications.
-
D.
ISO Code of Conduct for technical work
The ISO Code of Conduct for technical work is a set of principles and rules that guide the behavior, integrity, and impartiality of participants involved in developing international standards within ISO’s technical committees and working groups.
-
E.
IETF meetings
IETF meetings are regular international gatherings where Internet standards are discussed, developed, and coordinated by the Internet Engineering Task Force and its working groups.
- 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 code of conduct Target entity description: The IETF code of conduct is a set of rules and guidelines that define acceptable behavior and promote respectful, professional interaction within the Internet Engineering Task Force community.
-
A.
IETF governance
IETF governance refers to the structures, processes, and decision-making practices that guide how the Internet Engineering Task Force develops, maintains, and evolves open internet standards.
-
B.
IETF community
The IETF community is the global, open network of engineers, researchers, and other stakeholders who collaboratively develop and maintain Internet standards and related technical documents.
-
C.
IETF BEHAVE working group
The IETF BEHAVE working group was a standards body group within the Internet Engineering Task Force focused on defining and improving how Network Address Translators (NATs) interact with Internet protocols and applications.
-
D.
ISO Code of Conduct for technical work
The ISO Code of Conduct for technical work is a set of principles and rules that guide the behavior, integrity, and impartiality of participants involved in developing international standards within ISO’s technical committees and working groups.
-
E.
IETF meetings
IETF meetings are regular international gatherings where Internet standards are discussed, developed, and coordinated by the Internet Engineering Task Force and its working groups.
- 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_69e2458426188190b58b8ab4844fe420 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17dcb872881909a031d8560635fce |
completed | April 29, 2026, 3:40 a.m. |
Created at: April 17, 2026, 3:33 p.m.