Triple
T11294981
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | STPF |
E267426
|
entity |
| Predicate | benefitToFellows |
P487
|
FINISHED |
| Object | hands-on policy experience |
—
|
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: hands-on policy experience | Statement: [STPF, benefitToFellows, hands-on policy experience]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: benefitToFellows Context triple: [STPF, benefitToFellows, hands-on policy experience]
-
A.
benefitsAre
Indicates that certain advantages, gains, or positive outcomes are possessed by or accrue to a particular entity or group.
-
B.
indicatesFellowshipIn
Indicates that one entity holds a fellowship position, membership, or sponsored research role within another entity (such as an institution, organization, or program).
-
C.
benefits
chosen
Indicates that one entity gains an advantage, improvement, or positive outcome as a result of another entity or action.
-
D.
benefitForFaculty
Indicates that something provides an advantage, support, or positive outcome specifically for faculty members.
-
E.
offersFellowshipPrograms
Indicates that an entity provides or makes available fellowship programs to individuals or other entities.
- 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_69d6aac993a08190a6f36445ebaf9a43 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e98b149481909f432a6b9ef8bfbb |
completed | April 9, 2026, 6:01 p.m. |
| PD | Predicate disambiguation | batch_69d787a6ca2c8190afdc24b61ccd3f8a |
completed | April 9, 2026, 11:04 a.m. |
Created at: April 8, 2026, 9:32 p.m.