Triple
T32237952
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Малка |
E823521
|
entity |
| Predicate | находится в субъекте РФ |
P127825
|
FINISHED |
| Object | Кабардино-Балкарская Республика |
—
|
NE NERFINISHED |
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: Кабардино-Балкарская Республика | Statement: [Малка, находится в субъекте РФ, Кабардино-Балкарская Республика]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: находится в субъекте РФ Context triple: [Малка, находится в субъекте РФ, Кабардино-Балкарская Республика]
-
A.
находитсяВСтране
Indicates that something is located within the territory or borders of a specific country.
-
B.
locatedInRegionOfRussia
chosen
Indicates that one entity is geographically situated within a specified region of Russia.
-
C.
containsFederalSubject
Indicates that one administrative or territorial entity includes a specific federal subject within its jurisdiction or boundaries.
-
D.
находитсяК
Indicates that one entity is located at, in, or near another entity.
-
E.
устьеНаходитсяВ
Indicates that the mouth of a river or stream is located within or at a specified body of water 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_69f3490c140481908ed53b98b561eaa1 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bbff8f9c8190b82aaba0947c5785 |
completed | May 3, 2026, 3:07 a.m. |
| PD | Predicate disambiguation | batch_69f6b632cf788190a3d0c08cd026b84b |
completed | May 3, 2026, 2:42 a.m. |
Created at: May 1, 2026, 12:39 a.m.