Triple

T36798404
Position Surface form Disambiguated ID Type / Status
Subject Polski Trambesh E909250 entity
Predicate hasTransportRoleIn P194193 FINISHED
Object Veliko Tarnovo Province 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: Veliko Tarnovo Province | Statement: [Polski Trambesh, hasTransportRoleIn, Veliko Tarnovo Province]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasTransportRoleIn
Context triple: [Polski Trambesh, hasTransportRoleIn, Veliko Tarnovo Province]
  • A. hasRoleInTransport chosen
    Indicates that an entity participates in a transport process by holding a specific functional role within that transport.
  • B. hasCargoRole
    Indicates that an entity participates in a cargo-related capacity or function within a transport, shipment, or logistics context.
  • C. hasIntermodalRole
    Indicates that an entity plays a specific role or function within an intermodal (multi-mode) transportation or logistics context.
  • D. hasTransportAuthority
    Indicates that one entity holds official power or responsibility to manage, regulate, or oversee transportation services or infrastructure for another entity or area.
  • E. hasPassengerRole
    Indicates that an entity participates in a context or event specifically in the capacity or role of a passenger.
  • 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_69f76e7b98888190899b6478a82ad6ae completed May 3, 2026, 3:49 p.m.
NER Named-entity recognition batch_6a00037bf4148190a58593d30efdd3f8 completed May 10, 2026, 4:03 a.m.
PD Predicate disambiguation batch_6a0000b7af608190b718fc4111bcdad8 completed May 10, 2026, 3:51 a.m.
Created at: May 3, 2026, 4:12 p.m.