Triple
T6664596
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European Agricultural Fund for Rural Development |
E151566
|
entity |
| Predicate | coFinancing |
P3260
|
FINISHED |
| Object | national public funds |
—
|
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: national public funds | Statement: [European Agricultural Fund for Rural Development, coFinancing, national public funds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coFinancing Context triple: [European Agricultural Fund for Rural Development, coFinancing, national public funds]
-
A.
fundingContext
Indicates the circumstances, purpose, or conditions under which funding is provided or used in a given relationship or action.
-
B.
coFounderWith
Indicates that two or more entities jointly founded the same organization or venture.
-
C.
coSponsor
chosen
Indicates that an entity jointly supports, endorses, or backs an initiative, proposal, or activity together with one or more others.
-
D.
fundedBy
Indicates that an entity receives financial support or resources from another entity.
-
E.
fundingModel
Indicates how an entity is financially supported or sustained, such as through specific revenue sources, payment structures, or funding mechanisms.
- 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_69c687f5fac48190a09e4838d9c6b45d |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6ce738fe88190a5557900efeec7ec |
completed | March 27, 2026, 6:37 p.m. |
| PD | Predicate disambiguation | batch_69c6ad09974c81908784300ae218961f |
completed | March 27, 2026, 4:15 p.m. |
Created at: March 27, 2026, 2:02 p.m.