Triple
T31818457
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BNT162b2 |
E812198
|
entity |
| Predicate | wasFirstAuthorizedIn |
P62673
|
FINISHED |
| Object | United Kingdom |
—
|
NE NERFINISHED |
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: United Kingdom | Statement: [BNT162b2, wasFirstAuthorizedIn, United Kingdom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasFirstAuthorizedIn Context triple: [BNT162b2, wasFirstAuthorizedIn, United Kingdom]
-
A.
firstToAuthorize
chosen
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.
-
B.
usedToAuthorize
Indicates that something serves as the basis or instrument for granting permission, approval, or official power to perform an action.
-
C.
wasFirst
Indicates that one entity occurred, appeared, or held a position before another in time or sequence.
-
D.
wasFirstApprovedIn
Indicates the time or context in which something (such as a proposal, product, or document) received its initial official approval.
-
E.
wasFirstApprovedFor
Indicates that an entity received its initial or earliest official approval specifically for another entity or purpose.
- 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_69f6af7f24a881909e6ae0d937e90ea2 |
completed | May 3, 2026, 2:14 a.m. |
| PD | Predicate disambiguation | batch_69f6aca59d4881908d14ed47962703bd |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 30, 2026, 11:45 p.m.