Triple
T20346041
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Russia–Azerbaijan border |
E495872
|
entity |
| Predicate | languageUsedAtBorder |
P77518
|
FINISHED |
| Object | Russian |
—
|
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: Russian | Statement: [Russia–Azerbaijan border, languageUsedAtBorder, Russian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageUsedAtBorder Context triple: [Russia–Azerbaijan border, languageUsedAtBorder, Russian]
-
A.
languageAlongBorder
chosen
Indicates that a particular language is spoken or prevalent along the border between two regions or entities.
-
B.
hasLanguageOfSurroundingCountries
Indicates that an entity uses or includes the languages commonly spoken in the countries that geographically surround it.
-
C.
hasOfficialLanguageOfSurroundingCountry
Indicates that an entity uses as its official language the same language that is official in the country surrounding it.
-
D.
borderDialectOf
Indicates a dialect that is spoken in a border area and is linguistically associated with or derived from a particular neighboring language or dialect.
-
E.
languageUsedInLocality
Indicates that a particular language is used or spoken within a specific locality or geographic area.
- 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_69e0b4a3320881909495ae8bc30bc2dc |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6783937a48190ac86e4959a781a2b |
completed | April 20, 2026, 7:02 p.m. |
| PD | Predicate disambiguation | batch_69e57636b4808190bc2855af48a3ccdc |
completed | April 20, 2026, 12:41 a.m. |
Created at: April 16, 2026, 11:24 a.m.