Triple
T32498297
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Message-Digest Algorithm 5 |
E830584
|
entity |
| Predicate | firstCollisionPublishedYear |
P206297
|
FINISHED |
| Object | 2004 |
—
|
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: 2004 | Statement: [Message-Digest Algorithm 5, firstCollisionPublishedYear, 2004]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstCollisionPublishedYear Context triple: [Message-Digest Algorithm 5, firstCollisionPublishedYear, 2004]
-
A.
firstCollisionsYear
Indicates the year in which the first collisions or interaction events occurred between the relevant entities.
-
B.
firstPublishedInWorkYear
Indicates the year in which a work was first published.
-
C.
firstAssociatedPublicationYear
Indicates the calendar year in which an entity’s earliest associated publication was first released or made publicly available.
-
D.
firstCompletePublicationYear
Indicates the calendar year in which an entity’s first complete publication was released.
-
E.
firstStandardPublicationYear
Indicates the year in which an entity’s work was first formally published according to a recognized standard or official publication record.
- 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_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379edf2d88190b492fca86ed23cac |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7fb9f88190b384b1b68200aef0 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 1, 2026, 12:59 a.m.