Triple
T31080847
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heartbleed |
E792089
|
entity |
| Predicate | datePubliclyReported |
P48219
|
FINISHED |
| Object | 2014-04-07 |
—
|
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: 2014-04-07 | Statement: [Heartbleed, datePubliclyReported, 2014-04-07]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: datePubliclyReported Context triple: [Heartbleed, datePubliclyReported, 2014-04-07]
-
A.
dataReportedAs
Indicates that specific information has been communicated or recorded in a particular stated form, value, or representation.
-
B.
dataReportedBy
Indicates that certain data has been provided, recorded, or communicated by a specific source or reporting entity.
-
C.
dateOfHIVStatusPublicDisclosure
Indicates the date on which an individual's HIV status was first publicly disclosed or made known to others.
-
D.
isReportedAt
Indicates that an event, fact, or occurrence is documented or made known at a particular time, place, or reporting source.
-
E.
yearOfPublicDisclosure
chosen
Indicates the calendar year in which information, an invention, or other subject matter was first publicly disclosed.
- 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_69f224ccdbbc81909b0cdb4cc2d70c7a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f695f9fe7c819084322bf6cdc70a13 |
completed | May 3, 2026, 12:25 a.m. |
| PD | Predicate disambiguation | batch_69f690f13d7481908ddfefe95df2a1c2 |
completed | May 3, 2026, 12:04 a.m. |
Created at: April 29, 2026, 9:02 p.m.