Triple
T31080850
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heartbleed |
E792089
|
entity |
| Predicate | discoveredByOrganization |
P113006
|
FINISHED |
| Object | Google Security Team |
—
|
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: Google Security Team | Statement: [Heartbleed, discoveredByOrganization, Google Security Team]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: discoveredByOrganization Context triple: [Heartbleed, discoveredByOrganization, Google Security Team]
-
A.
introducedByOrganization
Indicates that an entity was brought into existence, presented, or launched by a specific organization.
-
B.
foundedOrganization
Indicates that an entity established or created an organization.
-
C.
isDiscoveredBy
chosen
Indicates that something (such as an object, fact, or phenomenon) is found, identified, or revealed by a particular agent or entity.
-
D.
introducedOrganization
Indicates that one entity caused or facilitated the first formal appearance or presentation of an organization to another context, audience, or system.
-
E.
foundingOrganization
Indicates the organization that established or created another entity, such as a company, institution, or project.
- 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_69f73223675481908c1bc3208c0f5284 |
completed | May 3, 2026, 11:31 a.m. |
| PD | Predicate disambiguation | batch_69f7317690108190b3aae2cd2e1d069e |
completed | May 3, 2026, 11:28 a.m. |
Created at: April 29, 2026, 9:02 p.m.