Triple
T19088729
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swedish research councils |
E467224
|
entity |
| Predicate | fundingScope |
P72661
|
FINISHED |
| Object | basic 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: basic research | Statement: [Swedish research councils, fundingScope, basic research]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fundingScope Context triple: [Swedish research councils, fundingScope, basic research]
-
A.
fundingFocus
chosen
Indicates that one entity’s funding is directed toward or prioritized for a particular target, theme, or area of activity.
-
B.
fundingContext
Indicates the circumstances, purpose, or conditions under which funding is provided or used in a given relationship or action.
-
C.
fundingFramework
Indicates that one entity provides the structural or regulatory basis that governs how funding is allocated, managed, or distributed to another entity or activity.
-
D.
fundingObjective
Indicates the purpose or goal for which financial resources are being sought, allocated, or used.
-
E.
fundingComponent
Indicates that one entity serves as a financial contributor or funding source for another entity or activity.
- 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_69d8dd05ac4c8190b1967d8f97f3fb2f |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e34981648190a89b006831846940 |
completed | April 20, 2026, 8:26 a.m. |
| PD | Predicate disambiguation | batch_69e4b9a604308190a3235184f9f2c056 |
completed | April 19, 2026, 11:16 a.m. |
Created at: April 10, 2026, 12:04 p.m.