Triple
T8942630
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oripää |
E212939
|
entity |
| Predicate | unilingual |
P4185
|
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: [Oripää, unilingual, Finnish]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: unilingual Context triple: [Oripää, unilingual, Finnish]
-
A.
languageIndependence
Indicates that a concept, method, or representation does not depend on any specific programming or natural language and can be applied uniformly across different languages.
-
B.
isLanguageOf
chosen
Indicates that a particular language is used as the official or primary language associated with a given entity (such as a person, document, or region).
-
C.
otherLanguage
Indicates that an entity has or uses an additional language distinct from its primary or main language.
-
D.
macrolanguageOf
Indicates that one language functions as a macrolanguage encompassing or grouping together one or more related individual languages.
-
E.
laterLanguageDominant
Indicates that one language becomes the dominant or primary language for an entity at a later point in time, after another language previously held that role.
- 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_69ca839694c88190b324ffeb43d23b08 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc66d93978819084b1a5c7c5dd2372 |
completed | April 1, 2026, 12:29 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed5267c8190a43feb2a2f3df1ec |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 6:58 p.m.