Triple
T30436213
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Дом Советов РСФСР |
E774317
|
entity |
| Predicate | расположенВРайонеГорода |
P83410
|
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 one entity is located on the surface or area of another entity.
-
B.
locatedIn
Indicates that one entity exists or is situated within the spatial, administrative, or conceptual boundaries of another entity.
-
C.
locatedInRegionalDistrict
chosen
Indicates that one entity is geographically situated within the boundaries of a specified regional district.
-
D.
находитсяК
Indicates that one entity is located at, in, or near another entity.
-
E.
areLocatedAt
Indicates that one or more entities occupy or exist at a specific location or place.
- 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_69f22492d2a88190995ce8745d9becaa |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f697eabb048190bc01a830f14942c6 |
completed | May 3, 2026, 12:33 a.m. |
| PD | Predicate disambiguation | batch_69f69664142c8190bc695501056b0236 |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 8:07 p.m.