Triple
T4945904
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | insulin |
E111048
|
entity |
| Predicate | processedTo |
P60098
|
FINISHED |
| Object | proinsulin |
—
|
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: proinsulin | Statement: [insulin, processedTo, proinsulin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: processedTo Context triple: [insulin, processedTo, proinsulin]
-
A.
processingUse
Indicates that one entity uses or applies another entity as part of a processing or transformation activity.
-
B.
formedTo
Indicates that one entity was created, established, or organized for the purpose of serving, supporting, or enabling another entity or activity.
-
C.
compiledTo
Indicates that one artifact (such as source code) has been transformed into another, typically lower-level or executable form, through a compilation process.
-
D.
usedProcess
Indicates that an entity employed or applied a particular process to achieve a result or perform an action.
-
E.
processingOrder
Indicates the sequence or priority in which items, tasks, or requests are to be processed or handled.
- F. None of above. chosen
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_69bd441721cc819085c7e33fe0876818 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd70aa890c81908e685ec5e88cae1f |
completed | March 20, 2026, 4:07 p.m. |
| PD | Predicate disambiguation | batch_69bd6c3aa1388190b3e0c8ee1ba1e4fa |
completed | March 20, 2026, 3:48 p.m. |
| PDg | Predicate description generation | batch_69bd6fa2d2088190ae444d3d0e47d5d2 |
completed | March 20, 2026, 4:02 p.m. |
Created at: March 20, 2026, 1:31 p.m.