Triple
T3157319
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ville |
E66014
|
entity |
| Predicate | ISO639-1LanguageCode |
P5196
|
FINISHED |
| Object | fi |
—
|
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: fi | Statement: [Ville, ISO639-1LanguageCode, fi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ISO639-1LanguageCode Context triple: [Ville, ISO639-1LanguageCode, fi]
-
A.
ISO639CollectiveCode
Indicates that the relationship assigns or associates an ISO 639 collective language code (a code representing a group of related languages) to the relevant language entity or set of languages.
-
B.
ISO639-3CodeOfLanguage
Indicates that one entity is the ISO 639-3 three-letter language code assigned to the language represented by the other entity.
-
C.
languageCodeISO639-2
Indicates that an entity is associated with a language identified by its ISO 639-2 three-letter code.
-
D.
languageCodeISO639-1
chosen
Indicates that the subject entity is associated with the specified two-letter ISO 639-1 language code.
-
E.
sharesISO639-3CodeWith
Indicates that two language entities share the same ISO 639-3 code, meaning they are treated as the same language in that coding system.
- 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_69ad85850c1481908a9e9c6242238de2 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada5ec0da88190a83f3448ac76e98e |
completed | March 8, 2026, 4:38 p.m. |
| PD | Predicate disambiguation | batch_69ad9dfbf0348190952a6bca8fc5fed1 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:05 p.m.