Triple
T20301091
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tagrisso |
E505479
|
entity |
| Predicate | hasLegalStatusInUS |
P14939
|
FINISHED |
| Object | prescription only |
—
|
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: prescription only | Statement: [Tagrisso, hasLegalStatusInUS, prescription only]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLegalStatusInUS Context triple: [Tagrisso, hasLegalStatusInUS, prescription only]
-
A.
hasLegalStatus
Indicates that an entity possesses a particular legal classification, recognition, or standing under law.
-
B.
hasHighestLegalStatusWithinCountry
Indicates that an entity holds the topmost legally recognized status or rank within a specific country, above all other comparable statuses.
-
C.
statusInUnitedStates
chosen
Indicates the legal or official standing that an entity holds within the jurisdiction of the United States.
-
D.
hasLegalStatusOver
Indicates that one entity holds a recognized legal authority, jurisdiction, or standing in relation to another entity.
-
E.
usedLegalStatus
Indicates that one entity applies or relies on the legal status or classification of another entity in a given context.
- 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_69e0b4b8ab648190906e18538c250148 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6770c700c81909da247cef0d0f1eb |
completed | April 20, 2026, 6:57 p.m. |
| PD | Predicate disambiguation | batch_69e55b21b09081909e46691b6f45a07f |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 16, 2026, 11:17 a.m.