Triple
T32498313
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Message-Digest Algorithm 5 |
E830584
|
entity |
| Predicate | designPredecessor |
P123192
|
FINISHED |
| Object | MD4 |
—
|
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: MD4 | Statement: [Message-Digest Algorithm 5, designPredecessor, MD4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designPredecessor Context triple: [Message-Digest Algorithm 5, designPredecessor, MD4]
-
A.
predecessorDesign
chosen
Indicates that one design serves as the predecessor or earlier version in relation to another design.
-
B.
predecessor
Indicates that one entity comes before another in an ordered sequence or succession.
-
C.
predecessorProject
Indicates that one project temporally or logically comes before and leads into another project in a sequence or dependency chain.
-
D.
programPredecessor
Indicates that one program temporally or logically precedes another in a sequence or hierarchy of programs.
-
E.
madeByPredecessorOf
Indicates that something was created or produced by an entity that is a predecessor (e.g., earlier version, ancestor, or prior holder of a role) of another specified entity.
- 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_69f349219cb8819087e120f509629c1b |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fe6739d4dc8190ae7505c089bbac29 |
completed | May 8, 2026, 10:44 p.m. |
| PD | Predicate disambiguation | batch_69fe6541dffc81909c66a61ba69f38fc |
completed | May 8, 2026, 10:35 p.m. |
Created at: May 1, 2026, 12:59 a.m.