Triple

T23851733
Position Surface form Disambiguated ID Type / Status
Subject Соборная площадь E592186 entity
Predicate пространственнаяРоль P36280 FINISHED
Object узел городской планировочной структуры 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: узел городской планировочной структуры | Statement: [Соборная площадь, пространственнаяРоль, узел городской планировочной структуры]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: пространственнаяРоль
Context triple: [Соборная площадь, пространственнаяРоль, узел городской планировочной структуры]
  • A. spaceStationRole
    Indicates the functional role or duty an entity has in relation to a space station.
  • B. spaceSectorRole
    Indicates the functional role or responsibility an entity holds within a specific space sector or domain.
  • C. spansRole
    Indicates that a role or function extends across, covers, or applies to multiple elements, contexts, or periods.
  • D. spatialProperty chosen
    Indicates a relationship where one entity has a specific spatial characteristic, such as position, size, orientation, or geometric configuration in space, relative to a reference frame or other entities.
  • E. role
    Indicates the function, position, or responsibility that one entity holds in relation to another within a given context.
  • 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_69e25d221d908190b9b502ad31e66a3f completed April 17, 2026, 4:17 p.m.
NER Named-entity recognition batch_69f1c987c3208190bf3f210d12106927 completed April 29, 2026, 9:04 a.m.
PD Predicate disambiguation batch_69f1614612b481908c45d99e588882f9 completed April 29, 2026, 1:39 a.m.
Created at: April 17, 2026, 8:11 p.m.