Triple
T9639749
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uusikaupunki |
E233031
|
entity |
| Predicate | hasMunicipalLanguage |
P11430
|
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: [Uusikaupunki, hasMunicipalLanguage, Finnish]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMunicipalLanguage Context triple: [Uusikaupunki, hasMunicipalLanguage, Finnish]
-
A.
hasRepresentativeLanguage
Indicates that an entity is associated with a language that serves as its primary or officially recognized means of representation or communication.
-
B.
majorityLanguageOf
chosen
Indicates that a given language is the primary or most widely spoken language within a specified group, region, or entity.
-
C.
ethnicLanguageStatus
Indicates the status or role of a language in relation to a particular ethnic group (e.g., primary, secondary, heritage, or minority language).
-
D.
hasLanguageOfOfficialName
Indicates that an entity’s official name is expressed in a specified language.
-
E.
hasLanguageOfSurroundingCountries
Indicates that an entity uses or includes the languages commonly spoken in the countries that geographically surround it.
- 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_69ca848a5a908190aad251f4137b0c3a |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9b532aa4819087b56be6f5635126 |
completed | April 1, 2026, 10:25 p.m. |
| PD | Predicate disambiguation | batch_69ccd5b0263081908cf6df3eb07d71b0 |
completed | April 1, 2026, 8:22 a.m. |
Created at: March 30, 2026, 8:12 p.m.