Triple
T33388697
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Teprotumumab |
E854987
|
entity |
| Predicate | hasClinicalTrialPhaseAtApproval |
P92940
|
FINISHED |
| Object | Phase 3 |
—
|
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: Phase 3 | Statement: [Teprotumumab, hasClinicalTrialPhaseAtApproval, Phase 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasClinicalTrialPhaseAtApproval Context triple: [Teprotumumab, hasClinicalTrialPhaseAtApproval, Phase 3]
-
A.
clinicalTrialPhase
chosen
Indicates the specific phase or stage of development a clinical trial is in within the overall clinical research process.
-
B.
hasClinicalTrials
Indicates that there exist one or more clinical trials associated with the referenced entity.
-
C.
studiesPhase
Indicates that an entity conducts research or examination on a particular phase or stage of a process, project, or phenomenon.
-
D.
hasClinicalTrialsIn
Indicates that clinical trials related to an entity are being or have been conducted in a specified location or region.
-
E.
hasClinicalTrialIdentifier
Indicates that a clinical trial is associated with a specific identifying code or number used to uniquely reference it.
- 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_69f3496d54048190a1cb91fdd7caa6ea |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd44474ed48190ac372e4c88d762ed |
completed | May 8, 2026, 2:02 a.m. |
| PD | Predicate disambiguation | batch_69fd41ef28a48190a66959be5c964461 |
completed | May 8, 2026, 1:52 a.m. |
Created at: May 1, 2026, 1:35 a.m.