Triple
T17093462
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NewLink Genetics |
E414780
|
entity |
| Predicate | holdsRightsTo |
P61797
|
FINISHED |
| Object | Ebola vaccine technology licenses |
—
|
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: Ebola vaccine technology licenses | Statement: [NewLink Genetics, holdsRightsTo, Ebola vaccine technology licenses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: holdsRightsTo Context triple: [NewLink Genetics, holdsRightsTo, Ebola vaccine technology licenses]
-
A.
acquiredRightsTo
chosen
Indicates that one entity has obtained legal or contractual ownership, control, or usage rights over something previously held by another entity.
-
B.
hasRightsOver
Indicates that one entity possesses legal, moral, or formal entitlements or authority over another entity.
-
C.
rightsInclude
Indicates that one set of rights encompasses, contains, or subsumes another set of rights.
-
D.
hasLegalRight
Indicates that an entity possesses an officially recognized legal entitlement or permission to perform an action or hold a claim regarding another entity.
-
E.
heldRight
Indicates that one entity is being held on the right side of another entity.
- 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_69d886cfc8e88190b05ba466edd35591 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3dbfb89348190942984037bd3bd2e |
completed | April 18, 2026, 7:31 p.m. |
| PD | Predicate disambiguation | batch_69e35d67b14481909fcdbdeaa5c34785 |
completed | April 18, 2026, 10:31 a.m. |
Created at: April 10, 2026, 5:35 a.m.