Triple
T29841921
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bishop of Espoo |
E757822
|
entity |
| Predicate | languageOfOfficialDuties |
P198236
|
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: [Bishop of Espoo, languageOfOfficialDuties, Finnish]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageOfOfficialDuties Context triple: [Bishop of Espoo, languageOfOfficialDuties, Finnish]
-
A.
languageOfOfficialAnnouncements
Indicates the language used for formal or official public announcements issued by an authority.
-
B.
usesOfficialLanguageOf
Indicates that one entity adopts and employs the official language of another entity for communication or formal purposes.
-
C.
officialLanguage
Indicates that a particular language has been formally designated by an authority as the official language used for government, legal, or administrative purposes in a given jurisdiction.
-
D.
languageOfOfficialReports
Indicates the language in which an entity’s official reports are written or issued.
-
E.
hasLanguageOfficial
Indicates that a language holds official status within a given entity, such as a country, region, or organization.
- 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_69f224593f6c81908785a560fe659f58 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fed48d8e148190a99c0aea29f8a3ee |
completed | May 9, 2026, 6:30 a.m. |
| PD | Predicate disambiguation | batch_69fed3c82a24819095e614e31ac0307f |
completed | May 9, 2026, 6:27 a.m. |
| PDg | Predicate description generation | batch_69fed48c92ec8190b3be88880d86de86 |
completed | May 9, 2026, 6:30 a.m. |
Created at: April 29, 2026, 5:39 p.m.