Triple
T28616023
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HeapFree |
E724273
|
entity |
| Predicate | linkage |
P20417
|
FINISHED |
| Object | import library Kernel32.lib |
—
|
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: import library Kernel32.lib | Statement: [HeapFree, linkage, import library Kernel32.lib]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: linkage Context triple: [HeapFree, linkage, import library Kernel32.lib]
-
A.
linkType
chosen
Indicates the specific kind or category of relationship that connects two linked entities.
-
B.
linkedByStructure
Indicates that two entities are connected or associated through a shared structural element, configuration, or framework.
-
C.
linkedPractice
Indicates that one practice is associated or connected to another practice in a meaningful or relevant way.
-
D.
binding
Indicates that one entity physically or chemically attaches, adheres, or forms a stable association with another entity.
-
E.
linkedSupport
Indicates a relationship where one entity provides support that is directly connected or dependent on another entity’s support or status.
- 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_69f01d816d7c8190a1fe27e3434041dc |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f652a492108190b885b955ce147d3c |
completed | May 2, 2026, 7:38 p.m. |
| PD | Predicate disambiguation | batch_69f651aad92c8190b874b3b5f9f64434 |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 28, 2026, 4:31 a.m.