Triple
T33389120
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ENSEMBLE |
E854996
|
entity |
| Predicate | trialCategory |
P177400
|
FINISHED |
| Object | pivotal efficacy 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: pivotal efficacy trial | Statement: [ENSEMBLE, trialCategory, pivotal efficacy trial]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trialCategory Context triple: [ENSEMBLE, trialCategory, pivotal efficacy trial]
-
A.
trialName
Indicates the designated name or title assigned to a specific trial.
-
B.
trialInstance
Indicates that one entity is a specific occurrence or execution of a broader trial, experiment, or test.
-
C.
trialBelongsTo
Indicates that a specific trial is associated with, or is a part of, a particular larger entity such as a study, project, or case.
-
D.
trialHeld
Indicates that a formal legal proceeding or court trial has taken place regarding a particular case or dispute.
-
E.
trial
Indicates that an entity is the subject of a legal or formal judicial proceeding to determine guilt, liability, or resolution of a dispute.
- 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_69f3496d54048190a1cb91fdd7caa6ea |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6fb93224881908fc66fe76115fcdb |
completed | May 3, 2026, 7:38 a.m. |
| PD | Predicate disambiguation | batch_69f6f96badb08190994442c2aba840b1 |
completed | May 3, 2026, 7:29 a.m. |
| PDg | Predicate description generation | batch_69f6fb17d5ec81909091e37e1ddbe577 |
completed | May 3, 2026, 7:36 a.m. |
Created at: May 1, 2026, 1:35 a.m.