Triple
T1169389
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Plegridy |
E24878
|
entity |
| Predicate | wasApprovedInUS |
P14939
|
FINISHED |
| Object | 2014 |
—
|
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: 2014 | Statement: [Plegridy, wasApprovedInUS, 2014]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasApprovedInUS Context triple: [Plegridy, wasApprovedInUS, 2014]
-
A.
approvedBy
Indicates that an action, request, or item has received formal authorization or consent from a specified entity.
-
B.
statusInUnitedStates
chosen
Indicates the legal or official standing that an entity holds within the jurisdiction of the United States.
-
C.
approves
Indicates that one entity formally accepts, authorizes, or agrees to a proposal, action, or decision made by another entity.
-
D.
requiresAdviceAndApprovalOf
Indicates that one entity can proceed with an action or decision only if it first seeks guidance and obtains formal approval from another entity.
-
E.
requiresPriorJudicialApproval
Indicates that an action or decision can only be taken if it has been previously reviewed and authorized by a judicial authority.
- 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.