Triple
T2236408
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 6668 |
E49290
|
entity |
| Predicate | definesRegistry |
P37272
|
FINISHED |
| Object | MAC Algorithm Names for SSH |
—
|
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: MAC Algorithm Names for SSH | Statement: [RFC 6668, definesRegistry, MAC Algorithm Names for SSH]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesRegistry Context triple: [RFC 6668, definesRegistry, MAC Algorithm Names for SSH]
-
A.
maintainsRegistryOf
Indicates that one entity is responsible for keeping and updating an official record or list of another set of entities or items.
-
B.
registryType
Indicates the specific category or classification of a registry that an entity is associated with or recorded in.
-
C.
registryFunction
Indicates a function that is responsible for registering or recording entities, configurations, or events within a registry or central management system.
-
D.
registryName
Indicates that an entity is identified or labeled by a specific name within a registry or registration system.
-
E.
definesRegionAs
Indicates that one entity specifies or designates another entity as a particular region or regional scope.
- F. None of above. chosen
Provenance (4 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_69a88aa84bdc819086df50e9c20b301e |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc09573848190bf91eddcc2fa0061 |
completed | March 7, 2026, 6:07 a.m. |
| PD | Predicate disambiguation | batch_69abbdafc07881909101266a33ae7031 |
completed | March 7, 2026, 5:54 a.m. |
| PDg | Predicate description generation | batch_69abbf9c77fc8190a323bcaf644fb2c5 |
completed | March 7, 2026, 6:03 a.m. |
Created at: March 4, 2026, 7:47 p.m.