Triple
T29986797
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 2195 |
E761753
|
entity |
| Predicate | definesMechanismName |
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, definesMechanismName, CRAM-MD5]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesMechanismName Context triple: [RFC 2195, definesMechanismName, 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.
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.
-
C.
mechanismBy
Indicates that one entity occurs, is produced, or is brought about by means of another entity, which serves as its mechanism or causal process.
-
D.
hasMechName
Indicates that an entity is associated with a specific mechanical or machine-related name or designation.
-
E.
hasMechanism
Indicates that one entity operates, functions, or produces an effect through the specified mechanism or process.
- 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_69fd3a69f1e08190a11aed015bff0858 |
completed | May 8, 2026, 1:20 a.m. |
| PD | Predicate disambiguation | batch_69fd39124180819080ca7911d3515d6d |
completed | May 8, 2026, 1:14 a.m. |
Created at: April 29, 2026, 6:36 p.m.