Triple

T29022385
Position Surface form Disambiguated ID Type / Status
Subject Mozhayskoye Shosse E737486 entity
Predicate isPartOfDirection P6309 FINISHED
Object Mozhaysk direction from Moscow 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: Mozhaysk direction from Moscow | Statement: [Mozhayskoye Shosse, isPartOfDirection, Mozhaysk direction from Moscow]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isPartOfDirection
Context triple: [Mozhayskoye Shosse, isPartOfDirection, Mozhaysk direction from Moscow]
  • A. isDirection
    Indicates that one entity specifies or represents the orientation or course along which another entity moves, points, or is aligned.
  • B. isPartOfRoute chosen
    Indicates that something (such as a segment, stop, or step) belongs to and is contained within a larger route.
  • C. containsDirectionOf
    Indicates that one entity includes or encompasses the directional orientation or path associated with another entity.
  • D. hasStreetDirection
    Indicates that a street or road segment is associated with a specific directional orientation (e.g., northbound, east-west).
  • E. isDirectionalDistrictName
    Indicates that a district’s name includes or is based on a geographic direction (e.g., north, south, east, west) relative to some reference area.
  • 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_69f077ee19f881909af48f9cab00a2e5 completed April 28, 2026, 9:03 a.m.
NER Named-entity recognition batch_69fd485f57dc8190820365396d041991 completed May 8, 2026, 2:20 a.m.
PD Predicate disambiguation batch_69fd47d35da081908bec8901018d186c completed May 8, 2026, 2:17 a.m.
Created at: April 28, 2026, 9:50 a.m.