Triple
T1169363
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Plegridy |
E24878
|
entity |
| Predicate | hasLegalStatusEU |
P2250
|
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: [Plegridy, hasLegalStatusEU, prescription only]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLegalStatusEU Context triple: [Plegridy, hasLegalStatusEU, prescription only]
-
A.
europeanUnionStatus
Indicates whether an entity is a member of, associated with, or otherwise holds a defined status in relation to the European Union.
-
B.
hasMemberInEEA
Indicates that an entity has at least one member who is located in, based in, or belongs to the European Economic Area (EEA).
-
C.
hasLegalStatus
chosen
Indicates that an entity possesses a particular legal classification, recognition, or standing under law.
-
D.
hasEuropeanParliamentConstituency
Indicates that an entity is located within or represented by a specific European Parliament electoral constituency.
-
E.
hasSpecialLegalStatus
Indicates that an entity possesses a distinct, formally recognized legal standing or set of rights and obligations that differs from the standard legal status of comparable entities.
- 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_69a494082a7c819095004f423f294a64 |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bce821b481908bc278a3fa7973f4 |
completed | March 1, 2026, 10:25 p.m. |
| PD | Predicate disambiguation | batch_69a4bb5656948190b0b1d5446ad06005 |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:45 p.m.