Triple
T1279448
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gottfried Wilhelm Leibniz Prize |
E27289
|
entity |
| Predicate | useOfFunds |
P98
|
FINISHED |
| Object | to improve research conditions |
—
|
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: to improve research conditions | Statement: [Gottfried Wilhelm Leibniz Prize, useOfFunds, to improve research conditions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: useOfFunds Context triple: [Gottfried Wilhelm Leibniz Prize, useOfFunds, to improve research conditions]
-
A.
funds
Indicates that one entity provides financial resources or monetary support to another entity or activity.
-
B.
usedFor
chosen
Indicates that one entity serves a purpose, function, or role in accomplishing, enabling, or supporting another entity or activity.
-
C.
revenueUse
Indicates how generated revenue is allocated, spent, or applied toward specific purposes or activities.
-
D.
fundedBy
Indicates that an entity receives financial support or resources from another entity.
-
E.
fundsMayNotSupplant
Indicates that the specified funds must not replace or reduce existing funding sources or expenditures that would otherwise have been used.
- 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_69a496d3710c8190955dee8bc0dacb50 |
completed | March 1, 2026, 7:43 p.m. |
| NER | Named-entity recognition | batch_69a4c092eb688190bf42bbd59e4ff289 |
completed | March 1, 2026, 10:41 p.m. |
| PD | Predicate disambiguation | batch_69a4bee276d8819092f71c5a1140bb61 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:50 p.m.