Triple
T4784934
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | REGN-EB3 |
E106452
|
entity |
| Predicate | clinicalTrialType |
P54033
|
FINISHED |
| Object | randomized controlled trial |
—
|
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: randomized controlled trial | Statement: [REGN-EB3, clinicalTrialType, randomized controlled trial]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: clinicalTrialType Context triple: [REGN-EB3, clinicalTrialType, randomized controlled trial]
-
A.
coordinatesClinicalTrialsFor
Indicates that one entity organizes, manages, or oversees the planning and execution of clinical trials on behalf of another entity.
-
B.
trialDesign
chosen
Indicates the specific structure, methodology, and procedural plan according to which a trial or experiment is conducted.
-
C.
hasKeyClinicalTrial
Indicates that an entity is associated with a primary or pivotal clinical trial that is especially important for its evaluation or approval.
-
D.
hasTypeOfExperiment
Indicates that an experiment is associated with or classified under a specific type or category of experiment.
-
E.
trialName
Indicates the designated name or title assigned to a specific trial.
- 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_69bd43f4a9588190bf73e20bc27c03cc |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd65ae49ec81908f16248d22d1155f |
completed | March 20, 2026, 3:20 p.m. |
| PD | Predicate disambiguation | batch_69bd622e1b408190806c15c61519fc74 |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:22 p.m.