Triple
T29986789
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 2195 |
E761753
|
entity |
| Predicate | definesSASLMechanism |
P8684
|
FINISHED |
| Object | CRAM-MD5 |
—
|
NE NERFINISHED |
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: CRAM-MD5 | Statement: [RFC 2195, definesSASLMechanism, CRAM-MD5]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesSASLMechanism Context triple: [RFC 2195, definesSASLMechanism, CRAM-MD5]
-
A.
definesMechanism
chosen
Indicates that one entity specifies or explains the underlying process or mechanism by which another entity operates or occurs.
-
B.
hasMechanism
Indicates that one entity operates, functions, or produces an effect through the specified mechanism or process.
-
C.
createsMechanismFor
Indicates that one entity brings about or establishes a means, process, or structure that enables or facilitates a particular function or outcome for another entity.
-
D.
authenticationProtocol
Indicates that a particular method or set of rules is used to verify the identity of an entity before granting access or performing an action.
-
E.
securityMechanism
Indicates a relationship where one entity serves as a means or method to protect another entity from threats, vulnerabilities, or unauthorized actions.
- 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_69f2246851148190b8e76206db94b105 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fd389cb28c819099a77e28d25f258a |
completed | May 8, 2026, 1:13 a.m. |
| PD | Predicate disambiguation | batch_69fd3826d8048190ada79a5868d1d7f3 |
completed | May 8, 2026, 1:11 a.m. |
Created at: April 29, 2026, 6:36 p.m.