Triple

T31056096
Position Surface form Disambiguated ID Type / Status
Subject Ploshcha Lenina–Vakzalnaja interchange E791401 entity
Predicate isMajorTransferHubIn P190500 FINISHED
Object Minsk Metro system 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: Minsk Metro system | Statement: [Ploshcha Lenina–Vakzalnaja interchange, isMajorTransferHubIn, Minsk Metro system]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isMajorTransferHubIn
Context triple: [Ploshcha Lenina–Vakzalnaja interchange, isMajorTransferHubIn, Minsk Metro system]
  • A. isMajorHubType
    Indicates that an entity functions as a primary or central hub within a larger network or system.
  • B. isMajorBusHub
    Indicates that a location serves as a primary node in the bus network, with high connectivity and significant passenger or route volume.
  • C. hasMajorHubIn
    Indicates that an entity maintains a primary or significant operational hub or center in a specified location.
  • D. isTransportHubType
    Indicates that something serves as or belongs to a particular category of transport hub (such as a station, port, or terminal).
  • E. isMajorHubInCountry
    Indicates that a location functions as a primary or central hub within a specified country, typically in terms of transport, commerce, or connectivity.
  • 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_69f224cb08908190ba71ad9aa87518ed completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_69fcc7779d248190afdb348a95375443 completed May 7, 2026, 5:10 p.m.
PD Predicate disambiguation batch_69fcc58566a0819082d5ea36e03bf0c6 completed May 7, 2026, 5:01 p.m.
PDg Predicate description generation batch_69fcc73264e08190b0b5917f32226fae completed May 7, 2026, 5:09 p.m.
Created at: April 29, 2026, 9 p.m.