Triple
T21154219
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SIGA Technologies |
E521269
|
entity |
| Predicate | hasBrandName |
P40804
|
FINISHED |
| Object | TPOXX |
—
|
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: TPOXX | Statement: [SIGA Technologies, hasBrandName, TPOXX]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: TPOXX Context triple: [SIGA Technologies, hasBrandName, TPOXX]
-
A.
TPOXX
chosen
TPOXX is an antiviral medication developed to treat smallpox infections, serving as a key biodefense countermeasure against orthopoxvirus threats.
-
B.
THPO
THPO is the acronym for a Tribal Historic Preservation Office, the tribal agency responsible for protecting and managing a Native American tribe’s cultural and historic resources.
-
C.
TTPP
TTPP is the ICAO airport code for Piarco International Airport, the main international gateway serving Trinidad and Tobago.
-
D.
TPA
TPA is an abbreviation commonly used for a Tri-Party Agreement, a legal contract involving three separate parties that defines their respective rights and obligations.
-
E.
TPA
TPA is the three-letter IATA airport code for Tampa International Airport, a major commercial airport serving the Tampa Bay area in Florida, USA.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0b50d1ea481909c07e63c3ead9316 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7252a48788190bfdfe811fc6cfc06 |
completed | April 21, 2026, 7:20 a.m. |
Created at: April 16, 2026, 2:58 p.m.