Triple
T32237959
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Малка |
E823521
|
entity |
| Predicate | расположена на территории |
P17086
|
FINISHED |
| Object | Российская Федерация |
—
|
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: Российская Федерация | Statement: [Малка, расположена на территории, Российская Федерация]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: расположена на территории Context triple: [Малка, расположена на территории, Российская Федерация]
-
A.
расположена в части страны
Indicates that one place or area is situated within a specific part or region of a country.
-
B.
расположенаНа
Indicates that one entity is located on the surface or area of another entity.
-
C.
representsTerritoryLocatedOn
Indicates that a specified territory is geographically situated on or within the bounds of a particular landmass or larger territorial unit.
-
D.
positionOnTerritory
Indicates that one entity occupies or is located at a specific position within the spatial extent of another entity’s territory.
-
E.
locatedOnTerritoryOf
chosen
Indicates that one entity is situated within or on the land area governed or owned by another entity.
- 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_69f6ba6cef208190bc5cd43d96127004 |
completed | May 3, 2026, 3:01 a.m. |
Created at: May 1, 2026, 12:39 a.m.