Triple
T30429266
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EU cohesion policy |
E774113
|
entity |
| Predicate | hadProgrammingPeriod |
P169766
|
FINISHED |
| Object | 2000–2006 programming period |
—
|
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 programming period | Statement: [EU cohesion policy, hadProgrammingPeriod, 2000–2006 programming period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadProgrammingPeriod Context triple: [EU cohesion policy, hadProgrammingPeriod, 2000–2006 programming period]
-
A.
hasProgramme
Indicates that an entity is associated with or offers a particular programme (such as a course of study, plan, or structured set of activities).
-
B.
hadGrowthPeriod
Indicates that an entity experienced a specific span of time during which it underwent growth or development.
-
C.
hasMainPeriod
Indicates that something is associated with or characterized by a primary or most significant time period.
-
D.
hadPractice
Indicates that an entity engaged in or participated in a practice session or rehearsal.
-
E.
hasHad
Indicates that an entity previously experienced, possessed, or was involved in something at some point in the past.
- F. None of above. chosen
Provenance (4 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_69f22492d2a88190995ce8745d9becaa |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6866aa9f88190b3e139fb374d6606 |
completed | May 2, 2026, 11:19 p.m. |
| PD | Predicate disambiguation | batch_69f67e40af9881908de3a4aa15f70a83 |
completed | May 2, 2026, 10:44 p.m. |
| PDg | Predicate description generation | batch_69f67f7e116c819099aec724e9ef3763 |
completed | May 2, 2026, 10:49 p.m. |
Created at: April 29, 2026, 8:06 p.m.