Triple
T22344162
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | lint |
E552347
|
entity |
| Predicate | doesNotPerform |
P4300
|
FINISHED |
| Object | dynamic analysis |
—
|
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: dynamic analysis | Statement: [lint, doesNotPerform, dynamic analysis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: doesNotPerform Context triple: [lint, doesNotPerform, dynamic analysis]
-
A.
doesNot
chosen
Indicates that a specified entity lacks, refrains from, or fails to perform a particular action or exhibit a particular property in relation to another entity or context.
-
B.
doesNotPrevent
Indicates that one entity or condition fails to stop, block, or inhibit another event, action, or state from occurring.
-
C.
doesNotUse
Indicates that one entity intentionally refrains from employing, utilizing, or relying on another entity, method, or resource.
-
D.
doesNotTry
Indicates that an entity makes no attempt to perform a particular action or engage in a specified activity.
-
E.
doesNotImpose
Indicates that one entity refrains from placing requirements, restrictions, or burdens upon another entity.
- 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_69e11e494eec81909c4d2d51f69499d9 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15796b2288190b10e9402abf35fd3 |
completed | April 29, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69e7300c20088190a59e5bf9e70384f3 |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:43 p.m.