Triple
T4325054
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Erasmus+ Programme Guide |
E96617
|
entity |
| Predicate | coversActionType |
P56248
|
FINISHED |
| Object | Key Action 1 |
—
|
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: Key Action 1 | Statement: [Erasmus+ Programme Guide, coversActionType, Key Action 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coversActionType Context triple: [Erasmus+ Programme Guide, coversActionType, Key Action 1]
-
A.
coversEvent
Indicates that one event includes, spans, or encompasses the time period or occurrence of another event.
-
B.
coversMode
Indicates that one entity includes, addresses, or supports a particular mode or manner of operation associated with another entity.
-
C.
coversTypeOfSite
Indicates that one entity provides coverage or applies to a particular category or type of site.
-
D.
typeOfCoverage
Indicates the specific kind or category of coverage that applies in a given context (such as insurance, service, or protection).
-
E.
typicallyCovers
Indicates that one entity is the kind of thing that usually or normally includes, addresses, or encompasses another entity.
- 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_69b34542fd908190b11b08faad8decfd |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3512ec18481908a7b5c29b3902b53 |
completed | March 12, 2026, 11:50 p.m. |
| PD | Predicate disambiguation | batch_69b34f4bec888190987fc2631498b637 |
completed | March 12, 2026, 11:42 p.m. |
| PDg | Predicate description generation | batch_69b3501834448190bedf775a80da4778 |
completed | March 12, 2026, 11:45 p.m. |
Created at: March 12, 2026, 11:13 p.m.