Triple
T37328941
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Philip Leverhulme Prize |
E926685
|
entity |
| Predicate | maximumDurationOfFunding |
P49263
|
FINISHED |
| Object | 3 years |
—
|
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: 3 years | Statement: [Philip Leverhulme Prize, maximumDurationOfFunding, 3 years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maximumDurationOfFunding Context triple: [Philip Leverhulme Prize, maximumDurationOfFunding, 3 years]
-
A.
fundingPeriod
chosen
Indicates the time span or duration for which funding is allocated, active, or valid within a financial or grant-related relationship.
-
B.
fundingPeriodEnd
Indicates the date or point in time when a particular funding arrangement, grant, or financial support comes to an end.
-
C.
fundingSpeed
Indicates how quickly financial resources are provided or disbursed within a given funding relationship or process.
-
D.
fundingCapType
Indicates the classification or category of a limit placed on the amount of funding that can be provided.
-
E.
maximumAccrualPeriod
Indicates the longest time span over which something (such as interest, benefits, or rights) can accumulate before it stops accruing.
- 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_69f76eb386d88190a8d511aa11540dfc |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd7b0503a08190ba07338365b6fcc9 |
completed | May 8, 2026, 5:56 a.m. |
| PD | Predicate disambiguation | batch_69fd7a9733dc81909199f453c0cc2bc1 |
completed | May 8, 2026, 5:54 a.m. |
Created at: May 3, 2026, 4:16 p.m.