Triple
T7168816
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prescription Drug User Fee Act of 1992 |
E167139
|
entity |
| Predicate | appliesToProcess |
P1129
|
FINISHED |
| Object | new drug application review |
—
|
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: new drug application review | Statement: [Prescription Drug User Fee Act of 1992, appliesToProcess, new drug application review]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesToProcess Context triple: [Prescription Drug User Fee Act of 1992, appliesToProcess, new drug application review]
-
A.
appliesTo
chosen
Indicates that something is relevant, valid, or has effect in relation to a particular entity, case, or context.
-
B.
appliesToFeature
Indicates that something (such as a rule, constraint, or configuration) is relevant to, or governs, a specific feature.
-
C.
appliesFrom
Indicates that a rule, condition, or effect begins to be applicable starting from a specific point in time or state.
-
D.
appliesToPolicy
Indicates that something is relevant or applicable to a particular policy.
-
E.
appliesToPhase
Indicates that a particular rule, condition, or action is relevant to and operates during a specific phase within a process or lifecycle.
- 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_69c68888c10c819095e0383020225758 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e85c606081909f76d76fc5b90bc8 |
completed | March 27, 2026, 8:28 p.m. |
| PD | Predicate disambiguation | batch_69c6e1cd5c948190a9113b23f7308c21 |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:48 p.m.