Triple
T24161255
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deutsche Welle |
E598843
|
entity |
| Predicate | DW AkademieRole |
P154823
|
FINISHED |
| Object | media development and journalism training |
—
|
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: media development and journalism training | Statement: [Deutsche Welle, DW AkademieRole, media development and journalism training]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: DW AkademieRole Context triple: [Deutsche Welle, DW AkademieRole, media development and journalism training]
-
A.
eraRole
Indicates the specific role, function, or capacity an entity has within a particular historical or temporal era.
-
B.
roleInWZRD
Indicates that an entity holds a specific role or function within the context of WZRD.
-
C.
roleInEdom
Indicates that one entity holds or fulfills a specific role, function, or position within the context of Edom.
-
D.
deFactoRole
Indicates that an entity effectively functions in a role or capacity in practice, even if that role is not formally or officially assigned.
-
E.
loreRole
Indicates the specific narrative or canonical function an entity fulfills within a fictional or mythological lore.
- 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_69e288cb0a3081909ef221744f274384 |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1e0e9cd6c81908c33242f19fcc034 |
completed | April 29, 2026, 10:43 a.m. |
| PD | Predicate disambiguation | batch_69f176585f3481909beb907de252cd98 |
completed | April 29, 2026, 3:09 a.m. |
| PDg | Predicate description generation | batch_69f1785afe3c81909be28986ffe944bf |
completed | April 29, 2026, 3:17 a.m. |
Created at: April 17, 2026, 11:32 p.m.