Triple
T1631790
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Network Working Group |
E35271
|
entity |
| Predicate | documentationPractice |
P19006
|
FINISHED |
| Object | open publication of protocol specifications |
—
|
LITERAL 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: open publication of protocol specifications | Statement: [Network Working Group, documentationPractice, open publication of protocol specifications]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: documentationPractice Context triple: [Network Working Group, documentationPractice, open publication of protocol specifications]
-
A.
documentationStandard
Indicates that there is a specified convention or set of rules governing how documentation should be written, structured, or maintained in relation to an entity or process.
-
B.
documentationType
chosen
Indicates the specific category or kind of documentation associated with or required for an entity or process.
-
C.
practice
Indicates that an entity regularly performs an activity or skill, typically to improve proficiency or maintain competence.
-
D.
documentationUI
Indicates a relationship where a user interface element is used to present, navigate, or interact with documentation content.
-
E.
documentedBy
Indicates that something is recorded, described, or evidenced in a specific document or set of documents.
- F. None of above.
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_69a886036bc081909ff5de16dbe5e8ea |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a9431af5ac8190893133f1ae490142 |
completed | March 5, 2026, 8:47 a.m. |
| PD | Predicate disambiguation | batch_69a907c91c888190b6ed295c1a2e0977 |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:28 p.m.