Triple
T34549080
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Западный административный округ города Москвы |
E887011
|
entity |
| Predicate | пересекаетсяРекой |
P225
|
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.
crossedByRiver
chosen
Indicates that a river passes across or through a specified area, feature, or route.
-
B.
crossingOf
Indicates that one entity serves as the intersection or crossing point of two or more linear features, such as roads, paths, or tracks.
-
C.
crossesWatershed
Indicates that one entity passes from one drainage basin or watershed area into another, traversing the boundary between them.
-
D.
впадаетВБолееКрупнуюРеку
Indicates that a smaller river flows into and joins a larger river.
-
E.
separatesRiver
Indicates that a river serves as a dividing line or boundary between two entities.
- 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.