Triple
T29328409
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diagonal BiLSTM |
E743715
|
entity |
| Predicate | usedInTask |
P25490
|
FINISHED |
| Object | image generation |
—
|
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: image generation | Statement: [Diagonal BiLSTM, usedInTask, image generation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInTask Context triple: [Diagonal BiLSTM, usedInTask, image generation]
-
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.
usedInWorkBy
Indicates that something (such as a method, material, or concept) is employed or incorporated within a work created by a particular agent or author.
-
C.
usedInProject
Indicates that something (such as a resource, tool, or component) is employed or utilized within a particular project.
-
D.
areUsedIn
chosen
Indicates that certain entities serve as components, tools, or resources within a particular process, context, or application.
-
E.
usedInOperation
Indicates that something (such as a tool, method, or resource) is employed or applied during the execution of a particular operation or procedure.
- 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_69f09125f784819080f4e9fce9fe624f |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd13595c81908719f52c3d37a7e8 |
completed | May 6, 2026, 10:13 p.m. |
Created at: April 28, 2026, 1:28 p.m.