Triple
T38090483
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CVE-73 |
E951098
|
entity |
| Predicate | associatedTaskUnit |
—
|
GENERATED |
| Object | Taffy 3 |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedTaskUnit Context triple: [CVE-73, associatedTaskUnit, Taffy 3]
-
A.
associatedWithUnit
Indicates that one entity has a connection, linkage, or affiliation with a particular unit (such as a division, department, or organizational subunit).
-
B.
associatedUnitType
Indicates that one entity is linked to or characterized by a particular type or category of unit.
-
C.
assignedToUnit
chosen
Indicates that an entity (such as a person, resource, or task) is allocated or designated to a specific unit or organizational subdivision.
-
D.
associatedWorkKey
Indicates that there is a connection or linkage between one work and another related work, typically identifying the related work by a key or identifier.
-
E.
targetTask
Indicates that one entity is the specific task or objective that another entity is aiming to perform, achieve, or operate on.
- F. None of above.
Provenance (1 batch)
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_69f76f03a3608190a73fd6df87c792a8 |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:21 p.m.