Triple
T28594382
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Korean Wikidata |
E723734
|
entity |
| Predicate | supportsInterfaceLanguage |
P4149
|
FINISHED |
| Object | Korean |
—
|
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: Korean | Statement: [Korean Wikidata, supportsInterfaceLanguage, Korean]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsInterfaceLanguage Context triple: [Korean Wikidata, supportsInterfaceLanguage, Korean]
-
A.
usesLanguageSupport
Indicates that one entity makes use of language-related assistance, features, or services provided by another entity.
-
B.
isSupportedByLanguage
Indicates that something (such as a feature, format, or construct) is compatible with and can be handled or recognized by a particular language.
-
C.
languageOfInterface
chosen
Indicates the language used by or presented in a user interface.
-
D.
supportsLanguageOverrides
Indicates that an entity allows its default behavior or settings to be modified based on specific language selections or preferences.
-
E.
supportsInternationalization
Indicates that an entity provides functionality or features that enable use across multiple languages, locales, or regional formats.
- 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_69f01d80b1908190980594837604b8c7 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_6a012efebda88190a90c8f650e4b1ee9 |
completed | May 11, 2026, 1:21 a.m. |
| PD | Predicate disambiguation | batch_6a01298cc604819087c836659c128926 |
completed | May 11, 2026, 12:57 a.m. |
Created at: April 28, 2026, 4:21 a.m.