Triple
T24884161
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Клязьма |
E622801
|
entity |
| Predicate | протекает через регион |
P77740
|
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.
flowsThroughRegionType
Indicates that something such as a fluid, current, or pathway passes through and traverses a specified type of region.
-
B.
passesThroughAdministrativeRegion
chosen
Indicates that a route, path, or movement crosses into or through the territory of a specified administrative region.
-
C.
flowsInRegionWith
Indicates that something (such as a fluid, current, or process) moves or progresses within a specified geographic or spatial region.
-
D.
routeRegion
Indicates that a route is located within, passes through, or is associated with a particular geographic region.
-
E.
crossesRegion
Indicates that an entity moves through or passes across the spatial extent of a specified region.
- 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_69e2fac4aa848190b3446a3922cec150 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f43043512481909501a3979cac9947 |
completed | May 1, 2026, 4:46 a.m. |
| PD | Predicate disambiguation | batch_69f420fd375c81908ea4a4e60b76ee8f |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 5:25 a.m.