Triple
T34549065
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Западный административный округ города Москвы |
E887011
|
entity |
| Predicate | включаетРайон |
P22582
|
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.
regionOfCity
Indicates that a specified area or district is a constituent part or subdivision of a particular city.
-
B.
regionOfTown
Indicates that one entity is a specific area or district that forms part of a town.
-
C.
inCityDistrict
Indicates that one entity is located within the boundaries of a specific city district.
-
D.
includesDistrict
chosen
Indicates that one administrative or geographic entity contains or encompasses a specific district within its boundaries.
-
E.
zonesInclude
Indicates that one zone spatially or logically contains or encompasses another zone.
- 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_69f349cff89081908f91e0b064f4833e |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f720239d9881909ded0a06477fd9b8 |
completed | May 3, 2026, 10:14 a.m. |
| PD | Predicate disambiguation | batch_69f71cc8074c81909ae09bea2acf1a09 |
completed | May 3, 2026, 10 a.m. |
Created at: May 1, 2026, 2:02 a.m.