Triple
T32498288
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Message-Digest Algorithm 5 |
E830584
|
entity |
| Predicate | initialValueRegisterB |
P184020
|
FINISHED |
| Object | 0xefcdab89 |
—
|
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: 0xefcdab89 | Statement: [Message-Digest Algorithm 5, initialValueRegisterB, 0xefcdab89]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: initialValueRegisterB Context triple: [Message-Digest Algorithm 5, initialValueRegisterB, 0xefcdab89]
-
A.
initialValueRegisterA
Indicates that an entity serves as the initial value stored in or loaded into register A at the start of an operation or process.
-
B.
numberOfRegistersInitial
Indicates the initial count of registers associated with an entity at the start of a process or configuration.
-
C.
initialBlock
Indicates that something serves as the first or starting block in a sequence, structure, or process.
-
D.
initializer
Indicates the entity that sets up or prepares another entity, process, or structure for its initial state or first use.
-
E.
officialRegisterOf
Indicates that one entity serves as the authoritative, formally maintained record or registry for another entity.
- 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_69f349219cb8819087e120f509629c1b |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7aaabb58c8190bf81673608ecfb6e |
completed | May 3, 2026, 8:06 p.m. |
| PD | Predicate disambiguation | batch_69f7a8cec6d48190bebfa884b2f938c0 |
completed | May 3, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69f7aa6795f481908940838ee7041ff5 |
completed | May 3, 2026, 8:04 p.m. |
Created at: May 1, 2026, 12:59 a.m.