Triple
T31818458
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BNT162b2 |
E812198
|
entity |
| Predicate | hasFirstAuthorizationDate |
P68695
|
FINISHED |
| Object | 2020-12-02 |
—
|
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: 2020-12-02 | Statement: [BNT162b2, hasFirstAuthorizationDate, 2020-12-02]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFirstAuthorizationDate Context triple: [BNT162b2, hasFirstAuthorizationDate, 2020-12-02]
-
A.
wasFirstApprovedIn
chosen
Indicates the time or context in which something (such as a proposal, product, or document) received its initial official approval.
-
B.
firstToAuthorize
Indicates that one entity is the earliest or initial party to grant approval, permission, or authorization for a particular action or arrangement relative to others.
-
C.
wasFirstApprovedFor
Indicates that an entity received its initial or earliest official approval specifically for another entity or purpose.
-
D.
hasInceptionPeriod
Indicates the time span or period during which something begins or comes into existence.
-
E.
hasMaturityDate
Indicates the date on which an obligation, instrument, or agreement is scheduled to become due or reach the end of its term.
- 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_69f348e846c081908eb468a0665afd55 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fea2d0a4d08190aa06aeb902a02d5a |
completed | May 9, 2026, 2:58 a.m. |
| PD | Predicate disambiguation | batch_69fea24698348190b9b992a8e7cdbcd0 |
completed | May 9, 2026, 2:56 a.m. |
Created at: April 30, 2026, 11:45 p.m.