Triple
T32366732
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TENAYA |
E827013
|
entity |
| Predicate | developerOfInvestigationalDrug |
P97065
|
FINISHED |
| Object | Roche |
—
|
NE NERFINISHED |
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: Roche | Statement: [TENAYA, developerOfInvestigationalDrug, Roche]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: developerOfInvestigationalDrug Context triple: [TENAYA, developerOfInvestigationalDrug, Roche]
-
A.
coDeveloperDrug
chosen
Indicates a relationship where two or more entities jointly participate in the development of a drug.
-
B.
developedDrugFor
Indicates that one entity created or formulated a drug intended to treat or address a medical condition associated with another entity.
-
C.
clinicalTesting
Indicates that an entity is involved in or associated with the process of systematically testing medical interventions, treatments, or procedures in a clinical setting.
-
D.
chiefScientist
Indicates that one entity serves as the primary or lead scientist for another entity, typically holding top scientific authority or responsibility.
-
E.
coPrincipalInvestigator
Indicates that an entity serves jointly with another as a principal investigator on the same research project or grant.
- 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_69f349166d548190887b412fe908e2f4 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f9fd6834cc8190aa27153d6a99f3bb |
completed | May 5, 2026, 2:23 p.m. |
| PD | Predicate disambiguation | batch_69f7cf769338819092a5f42653dcc956 |
completed | May 3, 2026, 10:43 p.m. |
Created at: May 1, 2026, 12:50 a.m.