Triple
T6707272
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European Social Fund |
E153038
|
entity |
| Predicate | coFinancesWith |
P154
|
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 Social Fund, coFinancesWith, national public funds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coFinancesWith Context triple: [European Social Fund, coFinancesWith, national public funds]
-
A.
funds
chosen
Indicates that one entity provides financial resources or monetary support to another entity or activity.
-
B.
financeMinister
Indicates that one entity serves as the finance minister (or equivalent chief financial/government budget official) of another entity, typically a country or jurisdiction.
-
C.
finType
Indicates that an entity is of a finite type, meaning it has only a finite number of distinct possible values or elements.
-
D.
wealthSource
Indicates the relationship by which an entity obtains or derives its wealth from a particular source.
-
E.
banking
Indicates that an entity provides or engages in financial services such as holding deposits, managing accounts, or facilitating monetary transactions for 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_69c68808d8d8819087369015270788fe |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d16897e48190b43eda2206b14d6a |
completed | March 27, 2026, 6:50 p.m. |
| PD | Predicate disambiguation | batch_69c6d089c7488190a00853fb12f53b2a |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:06 p.m.