Triple
T17783508
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States Artists Fellowship |
E443955
|
entity |
| Predicate | fundingUseRestrictions |
P104847
|
FINISHED |
| Object | none |
—
|
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: none | Statement: [United States Artists Fellowship, fundingUseRestrictions, none]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fundingUseRestrictions Context triple: [United States Artists Fellowship, fundingUseRestrictions, none]
-
A.
excludedUseOfFundsFor
chosen
Indicates that certain funds are prohibited from being used for a specified purpose or activity.
-
B.
fundingPolicy
Indicates the rules or guidelines governing how financial resources are allocated, distributed, or managed within a given context.
-
C.
mandateRestriction
Indicates that an authority imposes a binding limitation or requirement on an entity’s actions or conditions.
-
D.
restrictedFromUseFor
Indicates that something is prohibited or limited from being used for a specified purpose, context, or application.
-
E.
permittedFundingFrom
Indicates that providing financial resources from one entity to another is allowed under specified rules or conditions.
- 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_69d8b9ef17708190bdf7e2adbf14ddc2 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e487234fc08190b590f20caa431463 |
completed | April 19, 2026, 7:41 a.m. |
| PD | Predicate disambiguation | batch_69e3d8d8e538819084f1584426b41d5e |
completed | April 18, 2026, 7:17 p.m. |
Created at: April 10, 2026, 10:12 a.m.