Triple
T9632114
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BioNTech |
E232831
|
entity |
| Predicate | hasClinicalTrialsIn |
P89361
|
FINISHED |
| Object | oncology |
—
|
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: oncology | Statement: [BioNTech, hasClinicalTrialsIn, oncology]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasClinicalTrialsIn Context triple: [BioNTech, hasClinicalTrialsIn, oncology]
-
A.
coordinatesClinicalTrialsFor
Indicates that one entity organizes, manages, or oversees the planning and execution of clinical trials on behalf of another entity.
-
B.
hasKeyClinicalTrial
Indicates that an entity is associated with a primary or pivotal clinical trial that is especially important for its evaluation or approval.
-
C.
hasResearchArm
Indicates that an entity includes or is associated with a specific research-focused component, group, or division.
-
D.
hasResearchStatus
Indicates that an entity holds a particular stage or condition within a research process, such as planned, in progress, completed, or published.
-
E.
hasPreclinicalFeature
Indicates that an entity exhibits a characteristic, sign, or attribute that is present before the full clinical manifestation of a condition or disease.
- 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_69ca848940cc8190b97cec654cb3bb4a |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9b2783b48190a9929dc3e3cd2956 |
completed | April 1, 2026, 10:24 p.m. |
| PD | Predicate disambiguation | batch_69ccd5acfa5c8190aaba3cf548723604 |
completed | April 1, 2026, 8:22 a.m. |
| PDg | Predicate description generation | batch_69ccd93fc45c8190a823305e461e581d |
completed | April 1, 2026, 8:37 a.m. |
Created at: March 30, 2026, 8:11 p.m.