Triple
T9931375
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MD5 |
E192654
|
entity |
| Predicate | collisionFirstPublicBreakYear |
P50447
|
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: [MD5, collisionFirstPublicBreakYear, 2004]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collisionFirstPublicBreakYear Context triple: [MD5, collisionFirstPublicBreakYear, 2004]
-
A.
firstCollisionsYear
chosen
Indicates the year in which the first collisions or interaction events occurred between the relevant entities.
-
B.
inscriptionYearOfFirstElements
Indicates the year in which the first elements of something (such as a site, object, or collection) were officially inscribed or recorded in a designated register or list.
-
C.
firstReportedYear
Indicates the year in which something was initially reported, documented, or made known for the first time.
-
D.
claimedYear
Indicates the year that is asserted or reported as being associated with an event, status, or fact, regardless of whether it is verified.
-
E.
firstCaptureYear
Indicates the year in which an entity was first captured or recorded as captured.
- 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_69ca82dd978c8190947124ab0d3315ac |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb5b54f348190b8e70e7beff6098a |
completed | April 2, 2026, 12:17 a.m. |
| PD | Predicate disambiguation | batch_69cd1d90b8a8819081748f129c0c6ab6 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:43 p.m.