Triple
T7110758
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FDC Act |
E165700
|
entity |
| Predicate | establishesAuthorityFor |
P9895
|
FINISHED |
| Object | new drug approval |
—
|
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 approval | Statement: [FDC Act, establishesAuthorityFor, new drug approval]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: establishesAuthorityFor Context triple: [FDC Act, establishesAuthorityFor, new drug approval]
-
A.
usesAuthorityOf
Indicates that one entity exercises power, rights, or influence derived from or on behalf of another entity’s authority.
-
B.
reaffirmsAuthorityOf
Indicates that one entity confirms, strengthens, or restates the legitimacy or power of another entity’s authority.
-
C.
recognizesAuthority
Indicates that one entity accepts, acknowledges, or submits to the power, control, or legitimate decision-making role of another entity.
-
D.
designatesAuthority
chosen
Indicates that one entity formally assigns or confers decision-making power or control over something to another entity.
-
E.
indicatesAuthorityOver
Indicates that one entity holds recognized power, control, or decision-making authority over another entity.
- 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_69c6888120f081908f8f01b201dc4a4c |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e5be09d881909988b5382ffa20ed |
completed | March 27, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69c6e1c4f9788190830288d00cc37026 |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:43 p.m.