Triple
T17598610
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pipfile.lock |
E428635
|
entity |
| Predicate | usedInWorkflow |
P25490
|
FINISHED |
| Object | deployment of Python applications |
—
|
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: deployment of Python applications | Statement: [Pipfile.lock, usedInWorkflow, deployment of Python applications]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInWorkflow Context triple: [Pipfile.lock, usedInWorkflow, deployment of Python applications]
-
A.
usedInWork
Indicates that something (such as a concept, method, material, or component) is employed or applied within a particular work, project, or creation.
-
B.
usedInOperation
Indicates that something (such as a tool, method, or resource) is employed or applied during the execution of a particular operation or procedure.
-
C.
usedInProject
Indicates that something (such as a resource, tool, or component) is employed or utilized within a particular project.
-
D.
hasWorkUsedBy
Indicates that a work (such as a resource, document, or artifact) is utilized or referenced by another entity in performing its activities or functions.
-
E.
areUsedIn
chosen
Indicates that certain entities serve as components, tools, or resources within a particular process, context, or application.
- 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_69d889e1030481909950e140c63255b9 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e46c474e5481909d2736241b592dab |
completed | April 19, 2026, 5:46 a.m. |
| PD | Predicate disambiguation | batch_69e3b4fff0348190b899a32da537eaca |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:51 a.m.