Triple
T31818468
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BNT162b2 |
E812198
|
entity |
| Predicate | wasKeyTrial |
P172631
|
FINISHED |
| Object | Phase 3 trial NCT04368728 |
—
|
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 trial NCT04368728 | Statement: [BNT162b2, wasKeyTrial, Phase 3 trial NCT04368728]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasKeyTrial Context triple: [BNT162b2, wasKeyTrial, Phase 3 trial NCT04368728]
-
A.
trialOccurredIn
Indicates that a particular trial took place within a specified location, venue, or jurisdiction.
-
B.
trialBasedOn
Indicates that a legal trial is conducted on the basis of, or in reliance upon, a specified prior case, evidence, rule, or authority.
-
C.
onTrialFor
Indicates that a person is currently being legally prosecuted or judged in court for a specific alleged offense or charge.
-
D.
trialName
Indicates the designated name or title assigned to a specific trial.
-
E.
relatedTrial
Indicates that one trial is associated with another trial, typically through relevance, similarity, or shared context within a broader study or legal/experimental framework.
- 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_69f348e846c081908eb468a0665afd55 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6b034bc74819091250f91ba5174c0 |
completed | May 3, 2026, 2:17 a.m. |
| PD | Predicate disambiguation | batch_69f6aca59d4881908d14ed47962703bd |
completed | May 3, 2026, 2:02 a.m. |
| PDg | Predicate description generation | batch_69f6af7d92008190aead47eaae8cc091 |
completed | May 3, 2026, 2:14 a.m. |
Created at: April 30, 2026, 11:45 p.m.