Triple
T28630681
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Turkish Wikidata |
E724630
|
entity |
| Predicate | supportsMultilingualData |
P11998
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Turkish Wikidata, supportsMultilingualData, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsMultilingualData Context triple: [Turkish Wikidata, supportsMultilingualData, true]
-
A.
isMultilingual
Indicates that an entity can understand and/or communicate in multiple languages.
-
B.
supportsInternationalization
chosen
Indicates that an entity provides functionality or features that enable use across multiple languages, locales, or regional formats.
-
C.
hasMultilingualPresence
Indicates that an entity maintains an active presence or representation in multiple languages.
-
D.
secondaryLanguageSupport
Indicates that an entity provides assistance, services, or functionality in an additional (non-primary) language.
-
E.
supportsLanguageOverrides
Indicates that an entity allows its default behavior or settings to be modified based on specific language selections or preferences.
- 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_69f01d8328c48190bc0e5f9b9b848582 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_6a01b31b233c819091974a06f7a76d4a |
completed | May 11, 2026, 10:44 a.m. |
| PD | Predicate disambiguation | batch_6a01b2c147008190bbf9e0fa1bbae1f3 |
completed | May 11, 2026, 10:43 a.m. |
Created at: April 28, 2026, 4:37 a.m.