Triple
T34214982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SR Sisuradio |
E877758
|
entity |
| Predicate | hasFinnishLanguageProgramming |
P199936
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [SR Sisuradio, hasFinnishLanguageProgramming, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFinnishLanguageProgramming Context triple: [SR Sisuradio, hasFinnishLanguageProgramming, true]
-
A.
hasLanguageOfProgramming
Indicates that an entity uses, is implemented in, or is otherwise associated with a particular programming language.
-
B.
primaryLanguageOfPrograms
Indicates that a given language is the main programming language used to implement or develop the specified programs.
-
C.
languageOfProgramNote
Indicates the language in which a given program note is written.
-
D.
alsoUsedLanguageInProgramming
Indicates that an entity used an additional programming language, beyond a primary one, in the context of programming.
-
E.
hasProgrammingFrom
Indicates that something derives its programming, configuration, or behavioral instructions from a specified source.
- 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_69f349b0b4bc819088c1552424089ee9 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff64b957bc81908afbc5914234a8ea |
completed | May 9, 2026, 4:45 p.m. |
| PD | Predicate disambiguation | batch_69ff6446593c81909173e296eea2590c |
completed | May 9, 2026, 4:43 p.m. |
| PDg | Predicate description generation | batch_69ff64b864f481909fcefc2b08595c89 |
completed | May 9, 2026, 4:45 p.m. |
Created at: May 1, 2026, 1:55 a.m.