Triple

T19799162
Position Surface form Disambiguated ID Type / Status
Subject Rostokino District E475623 entity
Predicate hasGoodTransportLinks P137371 FINISHED
Object yes 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: yes | Statement: [Rostokino District, hasGoodTransportLinks, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasGoodTransportLinks
Context triple: [Rostokino District, hasGoodTransportLinks, yes]
  • A. hasGoodPublicTransportConnections
    Indicates that an entity is well served by public transportation options, providing convenient and efficient connections to other locations.
  • B. hasPublicTransportConnection
    Indicates that there is an available public transportation link or service connecting the related entities.
  • C. hasPublicTransitRoute
    Indicates that there exists a public transportation route (such as a bus, train, or tram line) connecting or serving the related entities.
  • D. hasPublicTransitInfrastructure
    Indicates that a location or area is equipped with facilities and systems that support public transportation services (e.g., buses, trains, trams).
  • E. hasPublicTransitFunction
    Indicates that something serves a role or provides a service related to public transportation operations or infrastructure.
  • F. None of above. chosen

Provenance (4 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_69d8e51b014081908b263e167370529a completed April 10, 2026, 11:55 a.m.
NER Named-entity recognition batch_69e653c930a08190a2263db7170edd71 completed April 20, 2026, 4:26 p.m.
PD Predicate disambiguation batch_69e5305858108190bbbfdb9ba3ab9f80 completed April 19, 2026, 7:43 p.m.
PDg Predicate description generation batch_69e532bcf41c8190b685b5adf46a60fc completed April 19, 2026, 7:53 p.m.
Created at: April 10, 2026, 1:49 p.m.