Triple
T23233898
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cohesion Fund |
E581233
|
entity |
| Predicate | usedInProgrammingPeriod |
P59092
|
FINISHED |
| Object | 2000–2006 |
—
|
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: 2000–2006 | Statement: [Cohesion Fund, usedInProgrammingPeriod, 2000–2006]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInProgrammingPeriod Context triple: [Cohesion Fund, usedInProgrammingPeriod, 2000–2006]
-
A.
usedInProgrammingLanguages
Indicates that something (such as a concept, construct, or feature) is employed or implemented within one or more programming languages.
-
B.
programmingPeriod
chosen
Indicates the time span during which a programming activity, task, or project is carried out.
-
C.
hasProgrammingFrom
Indicates that something derives its programming, configuration, or behavioral instructions from a specified source.
-
D.
laterUsedForProgram
Indicates that something is subsequently utilized as part of, or as input to, a program or programming process.
-
E.
usedByProgram
Indicates that a particular resource, component, or element is utilized or consumed by a specific program.
- 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_69e2460556f88190be1744a84a84173f |
completed | April 17, 2026, 2:39 p.m. |
| NER | Named-entity recognition | batch_69f192e7bed88190b914b238c5f49860 |
completed | April 29, 2026, 5:11 a.m. |
| PD | Predicate disambiguation | batch_69effcdadec0819092ec1749ee453b4e |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 4:09 p.m.