Triple
T38090483
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CVE-73 |
E951098
|
entity |
| Predicate | associatedTaskUnit |
P93772
|
FINISHED |
| Object | Taffy 3 |
E268168
|
NE 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: Taffy 3 | Statement: [CVE-73, associatedTaskUnit, Taffy 3]
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 (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_69f76f03a3608190a73fd6df87c792a8 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037df1223c8190a5d61e4f8e6fd613 |
completed | May 12, 2026, 7:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a415d507c388190ad3281493a7fa752 |
completed | June 28, 2026, 5:43 p.m. |
| PD | Predicate disambiguation | batch_6a037a1ad6c48190bfe35d350c1b4751 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:21 p.m.