Triple
T2236391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 6668 |
E49290
|
entity |
| Predicate | definesMAC |
P37270
|
FINISHED |
| Object | hmac-sha2-256 |
—
|
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: hmac-sha2-256 | Statement: [RFC 6668, definesMAC, hmac-sha2-256]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesMAC Context triple: [RFC 6668, definesMAC, hmac-sha2-256]
-
A.
isMICFor
Indicates that one entity represents the minimum inhibitory concentration (MIC) value determined for another entity, typically a microorganism or drug.
-
B.
definesDeviceType
Indicates that one entity specifies or assigns the device type classification of another entity.
-
C.
definesFlag
Indicates that one entity specifies or establishes a particular flag or boolean indicator used by another entity or process.
-
D.
definesMechanism
Indicates that one entity specifies or explains the underlying process or mechanism by which another entity operates or occurs.
-
E.
hasMIC
Indicates that an entity has a specified Minimum Inhibitory Concentration (MIC) value in relation to an antimicrobial agent.
- 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.