Triple
T11178410
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vishnevo |
E264471
|
entity |
| Predicate | hasOfficialLanguageInCountry |
P96074
|
FINISHED |
| Object | Belarusian |
—
|
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: Belarusian | Statement: [Vishnevo, hasOfficialLanguageInCountry, Belarusian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOfficialLanguageInCountry Context triple: [Vishnevo, hasOfficialLanguageInCountry, Belarusian]
-
A.
hasOfficialCountryLanguage
Indicates that a country recognizes a particular language as one of its official languages for governmental or legal purposes.
-
B.
hasOfficialLanguageOfLocation
chosen
Indicates that a location has a specified language recognized as its official language.
-
C.
hasOfficialLanguageOfSurroundingCountry
Indicates that an entity uses as its official language the same language that is official in the country surrounding it.
-
D.
hasLanguageOfOfficialName
Indicates that an entity’s official name is expressed in a specified language.
-
E.
hasNotableLanguageWithOfficialStatusIn
Indicates that a language holds an officially recognized and notable status within a specified jurisdiction or region.
- 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_69d6aa9dafac8190bd90d2c74f661aa7 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e899c6288190b39e090fa9cdc883 |
completed | April 9, 2026, 5:57 p.m. |
| PD | Predicate disambiguation | batch_69d75cf0e6e88190973694abe2990973 |
completed | April 9, 2026, 8:01 a.m. |
Created at: April 8, 2026, 9:29 p.m.