Triple
T32279796
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | nivolumab |
E824658
|
entity |
| Predicate | firstApprovalCountry |
P37230
|
FINISHED |
| Object | Japan |
E174
|
NE 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: Japan | Statement: [nivolumab, firstApprovalCountry, Japan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstApprovalCountry Context triple: [nivolumab, firstApprovalCountry, Japan]
-
A.
countryOfApproval
Indicates that an item, action, or status has been officially approved or authorized by a particular country.
-
B.
authorizedCountry
Indicates that one entity (such as an activity, product, or permission) is officially allowed, recognized, or valid within the jurisdiction of a specified country.
-
C.
countryOfFirstAuthorization
chosen
Indicates the country in which an item (such as a product, work, or authorization-requiring entity) was first officially authorized or approved.
-
D.
eligibleCountry
Indicates that a given country meets the required criteria or conditions to qualify for a specified program, action, or status.
-
E.
firstForCountry
Indicates that the subject is the first instance or occurrence of its type to happen or exist within the specified country.
- F. None of above.
Provenance (4 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_69f3490f404081908450db66884f4334 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2f46d3b480819085838e49bc24b4e7 |
completed | June 15, 2026, 12:26 a.m. |
| PD | Predicate disambiguation | batch_6a0379edf2d88190b492fca86ed23cac |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 12:43 a.m.