Triple

T17655375
Position Surface form Disambiguated ID Type / Status
Subject Šlapanice E429607 entity
Predicate hasCommuterRoleFor P13163 FINISHED
Object Brno employment market 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: Brno employment market | Statement: [Šlapanice, hasCommuterRoleFor, Brno employment market]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasCommuterRoleFor
Context triple: [Šlapanice, hasCommuterRoleFor, Brno employment market]
  • A. hasCommuterOperator
    Indicates that an entity (such as a route, service, or station) is operated or served by a specific commuter transport operator.
  • B. isCommuterHub
    Indicates that a location functions as a central node where many commuters start, end, or transfer during their regular travel.
  • C. hasCommuterPattern
    Indicates that there is a characteristic or recurring pattern in how an entity regularly travels between locations, typically for work or daily activities.
  • D. hasCommuterLinks
    Indicates that there are established transportation connections enabling regular travel between two locations.
  • E. isCommuterRegionFor chosen
    Indicates that one region primarily serves as a residential base whose inhabitants regularly travel to another region for work or daily activities.
  • 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_69d889e2c2608190b762e76d9b2262f1 completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e46e40e344819086a49c69f8f2956b completed April 19, 2026, 5:55 a.m.
PD Predicate disambiguation batch_69e3cddc87188190ac2f049b86038676 completed April 18, 2026, 6:30 p.m.
Created at: April 10, 2026, 6:06 a.m.