Triple
T31080839
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heartbleed |
E792089
|
entity |
| Predicate | CWEID |
P170722
|
FINISHED |
| Object | CWE-125 |
—
|
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: CWE-125 | Statement: [Heartbleed, CWEID, CWE-125]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: CWEID Context triple: [Heartbleed, CWEID, CWE-125]
-
A.
ianaIdentifierType
Indicates that one entity specifies the type or category of an IANA (Internet Assigned Numbers Authority) identifier associated with another entity.
-
B.
identifiedIn
Indicates that an entity is recognized, discovered, or documented within a specified source, context, or location.
-
C.
GNDID
Indicates a standardized authority identifier linking an entity to its unique record in the Gemeinsame Normdatei (GND) authority file.
-
D.
identifierFor
Indicates that one entity serves as a unique identifying label or code for another entity.
-
E.
identifiedUsing
Indicates that one entity was recognized, distinguished, or determined by means of a specified method, tool, or identifier.
- 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_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. |
| PDg | Predicate description generation | batch_69f6938244648190a553b532387b812c |
completed | May 3, 2026, 12:14 a.m. |
Created at: April 29, 2026, 9:02 p.m.