Triple

T4465637
Position Surface form Disambiguated ID Type / Status
Subject Kyiv Metro E98369 entity
Predicate hasRollingStockOrigin P55577 FINISHED
Object Soviet-built trains 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: Soviet-built trains | Statement: [Kyiv Metro, hasRollingStockOrigin, Soviet-built trains]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasRollingStockOrigin
Context triple: [Kyiv Metro, hasRollingStockOrigin, Soviet-built trains]
  • A. usesRollingStock
    Indicates that one entity employs or operates specific rolling stock (such as rail vehicles) in its activities or services.
  • B. ownedRollingStock
    Indicates that one entity possesses or has ownership rights over specific rolling stock (such as trains, railcars, or locomotives).
  • C. usesRollingStockBrand
    Indicates that one entity employs or operates rolling stock manufactured under a specific brand.
  • D. usesRollingStockCompatibleWith
    Indicates that one entity operates using rolling stock that is technically and operationally compatible with the rolling stock standards or systems associated with another entity.
  • E. formerRollingStock
    Indicates that an entity was previously used as rolling stock (e.g., railway vehicles) but no longer serves in that capacity.
  • 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_69b3454a7c608190944f5455c8031d73 completed March 12, 2026, 10:59 p.m.
NER Named-entity recognition batch_69b356991a588190be2f95fd957d7f99 completed March 13, 2026, 12:13 a.m.
PD Predicate disambiguation batch_69b34f65f6448190abfadb2ae5658798 completed March 12, 2026, 11:42 p.m.
PDg Predicate description generation batch_69b34ff7018c81908ad8597e525c042b completed March 12, 2026, 11:44 p.m.
Created at: March 12, 2026, 11:34 p.m.