Triple
T8828714
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CRAM-MD5 |
E210079
|
entity |
| Predicate | protocolPhase |
P84870
|
FINISHED |
| Object | authentication phase |
—
|
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: authentication phase | Statement: [CRAM-MD5, protocolPhase, authentication phase]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: protocolPhase Context triple: [CRAM-MD5, protocolPhase, authentication phase]
-
A.
programPhase
Indicates the specific stage or phase within a broader program or process that an entity is currently associated with.
-
B.
protocol
Indicates that one entity defines or follows a specific set of rules or procedures governing how it interacts or communicates with another entity.
-
C.
protocolLayer
Indicates a relationship where a communication protocol operates at, or is associated with, a specific layer in a protocol stack or network architecture.
-
D.
phase2Purpose
Indicates the specific intended goal, function, or outcome associated with the second phase of a process or project.
-
E.
phase1Purpose
Indicates that one entity serves as the specific purpose, goal, or intended outcome of the first phase of another entity, process, or project.
- 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_69ca8365b28081909e48e45e95dfc405 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc604c52a48190807e46c15e3c1558 |
completed | April 1, 2026, 12:01 a.m. |
| PD | Predicate disambiguation | batch_69cc5c23d08481908d8c9b0ad3d1dc00 |
completed | March 31, 2026, 11:43 p.m. |
| PDg | Predicate description generation | batch_69cc5cff3608819081d2d7e5c16d44b7 |
completed | March 31, 2026, 11:47 p.m. |
Created at: March 30, 2026, 6:47 p.m.