Triple
T24637705
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pomerania Euroregion |
E609857
|
entity |
| Predicate | usesFunding |
P67
|
FINISHED |
| Object | European Union regional policy instruments |
—
|
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: European Union regional policy instruments | Statement: [Pomerania Euroregion, usesFunding, European Union regional policy instruments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesFunding Context triple: [Pomerania Euroregion, usesFunding, European Union regional policy instruments]
-
A.
usedFund
Indicates that one entity expended or applied a particular fund or financial resource for some purpose.
-
B.
includesFundingFor
Indicates that one entity’s financial resources or budget allocation explicitly cover or provide funding for another entity, project, or activity.
-
C.
fundingContext
Indicates the circumstances, purpose, or conditions under which funding is provided or used in a given relationship or action.
-
D.
usedFeederFunds
Indicates that an entity employed feeder funds as intermediary investment vehicles to channel capital into another fund or investment structure.
-
E.
fundedBy
chosen
Indicates that an entity receives financial support or resources from another entity.
- 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_69e2c4d28f848190ac38c400060e943d |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f2be064ff88190b5d9e5ec75a41242 |
completed | April 30, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f2a6d0ab708190b2e3b94dd20ca76b |
completed | April 30, 2026, 12:48 a.m. |
Created at: April 18, 2026, 2:33 a.m.