Triple
T25614266
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orphan Drug Act of 1983 |
E642116
|
entity |
| Predicate | typeOfIncentiveLaw |
P7916
|
FINISHED |
| Object | innovation incentive law |
—
|
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: innovation incentive law | Statement: [Orphan Drug Act of 1983, typeOfIncentiveLaw, innovation incentive law]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfIncentiveLaw Context triple: [Orphan Drug Act of 1983, typeOfIncentiveLaw, innovation incentive law]
-
A.
typeOfIncentive
chosen
Indicates the specific kind or category of incentive associated with an entity or action.
-
B.
containsLawType
Indicates that one entity includes or is associated with a specific type or category of law.
-
C.
providesIncentivesTo
Indicates that one entity offers rewards, benefits, or motivations to another entity to encourage a desired behavior or outcome.
-
D.
qualificationIncentive
Indicates that an incentive or benefit is provided contingent upon obtaining or holding a particular qualification.
-
E.
legalCodeType
Indicates the specific category or classification of a legal code that applies to an entity or situation.
- 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_69e77e7a96748190b10f2699041e4e43 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f71f8ee0688190bd025f27993452d3 |
completed | May 3, 2026, 10:12 a.m. |
| PD | Predicate disambiguation | batch_69f71cc405c08190863565609a4c8499 |
completed | May 3, 2026, 10 a.m. |
Created at: April 21, 2026, 4:58 p.m.