Triple
T14458197
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ministry of Justice of Finland |
E358509
|
entity |
| Predicate | appliesLanguage |
P76178
|
FINISHED |
| Object | Finnish |
—
|
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: Finnish | Statement: [Ministry of Justice of Finland, appliesLanguage, Finnish]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesLanguage Context triple: [Ministry of Justice of Finland, appliesLanguage, Finnish]
-
A.
usesLanguageFor
Indicates that an entity employs a particular language as a tool or medium to perform some activity, function, or purpose.
-
B.
usesLanguageAs
Indicates that one entity communicates or operates using another entity as its language or linguistic medium.
-
C.
adoptedLanguage
chosen
Indicates that an entity has chosen and begun using a particular language, typically as its official, primary, or preferred means of communication.
-
D.
languageAffected
Indicates that one entity has an impact on, modifies, or influences the characteristics, usage, or status of a language.
-
E.
suffixLanguage
Indicates that one language is used as a suffix or ending element in the formation or representation of another language or linguistic expression.
- 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_69d82794dfa081909b9134ad2e32244b |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de91aabebc819097eb61b2d81c9a91 |
completed | April 14, 2026, 7:12 p.m. |
| PD | Predicate disambiguation | batch_69de5c42bd3c81909a62acf30cc24d1e |
completed | April 14, 2026, 3:24 p.m. |
Created at: April 10, 2026, 1:19 a.m.