Triple
T27089298
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Klausman Institute for Medical Research |
E686116
|
entity |
| Predicate | targetField |
P134415
|
FINISHED |
| Object | clinical innovation |
—
|
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: clinical innovation | Statement: [Klausman Institute for Medical Research, targetField, clinical innovation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetField Context triple: [Klausman Institute for Medical Research, targetField, clinical innovation]
-
A.
targetsField
chosen
Indicates that one entity is directed toward, focuses on, or is intended to affect a specific field or attribute of another entity.
-
B.
target
Indicates that one entity is the intended object, goal, or focus of another entity’s action or attention.
-
C.
fromField
Indicates that something originates in, is sourced from, or is associated with a particular field or domain.
-
D.
targetProperty
Indicates that one entity serves as the intended goal, focus, or object of another entity’s action, influence, or effect.
-
E.
keyField
Indicates that the referenced field serves as a primary or unique identifier within a data structure or record.
- 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_69ef148940ec819097b5c20fbfbf7c81 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f707f7959881908f037f0d6b1d0c36 |
completed | May 3, 2026, 8:31 a.m. |
| PD | Predicate disambiguation | batch_69f700fc274c8190a128593dc7c7abd0 |
completed | May 3, 2026, 8:02 a.m. |
Created at: April 27, 2026, 8:40 a.m.