Triple
T31818481
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BNTX |
E812199
|
entity |
| Predicate | hasTickerSymbolFor |
P1447
|
FINISHED |
| Object | BioNTech SE |
—
|
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: BioNTech SE | Statement: [BNTX, hasTickerSymbolFor, BioNTech SE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTickerSymbolFor Context triple: [BNTX, hasTickerSymbolFor, BioNTech SE]
-
A.
tickerSymbol
chosen
Indicates the association between a financial instrument or company and its unique abbreviated code used for trading on a securities exchange.
-
B.
hasTickerCountryCode
Indicates that a financial instrument’s ticker symbol is associated with a specific country code.
-
C.
underlyingCompanyTicker
Indicates that one entity is the stock ticker symbol corresponding to the underlying company of another financial instrument or entity.
-
D.
hasCorporateTickerRoot
Indicates that a company’s stock ticker symbol is derived from or based on the specified root string.
-
E.
formerTickerSymbol
Indicates that one entity was previously used as the stock ticker symbol for another entity, but is no longer its current ticker symbol.
- 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_69fcf825ca7081909d06b0df33eb33f9 |
completed | May 7, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fcf42160f0819096812a8bf590875e |
completed | May 7, 2026, 8:20 p.m. |
Created at: April 30, 2026, 11:45 p.m.