Triple
T2249930
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ERC Synergy Grant |
E49591
|
entity |
| Predicate | fundingObjective |
P36498
|
FINISHED |
| Object | strengthen European frontier research |
—
|
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: strengthen European frontier research | Statement: [ERC Synergy Grant, fundingObjective, strengthen European frontier research]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fundingObjective Context triple: [ERC Synergy Grant, fundingObjective, strengthen European frontier research]
-
A.
fundedBy
Indicates that an entity receives financial support or resources from another entity.
-
B.
funderOf
Indicates that one entity provides financial support or funding for another entity, project, or activity.
-
C.
fundingModel
Indicates how an entity is financially supported or sustained, such as through specific revenue sources, payment structures, or funding mechanisms.
-
D.
funderType
Indicates the category or kind of organization or individual that provides funding in the relationship.
-
E.
purposeOfFoundation
Indicates the reason or intended goal for which an organization, institution, or entity was originally established.
- F. None of above. chosen
Provenance (4 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_69a88aa979788190ad6500f1d8eee2fc |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc11b61888190af3b11b87dc8e0dc |
completed | March 7, 2026, 6:09 a.m. |
| PD | Predicate disambiguation | batch_69abbdb160248190aa75b38f11ad8602 |
completed | March 7, 2026, 5:54 a.m. |
| PDg | Predicate description generation | batch_69abbe4252688190944491a450383450 |
completed | March 7, 2026, 5:57 a.m. |
Created at: March 4, 2026, 7:47 p.m.