Triple

T26007408
Position Surface form Disambiguated ID Type / Status
Subject Vaalimaa E646795 entity
Predicate hasBorderTrafficControl P165838 FINISHED
Object Finnish Border Guard 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: Finnish Border Guard | Statement: [Vaalimaa, hasBorderTrafficControl, Finnish Border Guard]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasBorderTrafficControl
Context triple: [Vaalimaa, hasBorderTrafficControl, Finnish Border Guard]
  • A. hasTrafficControl
    Indicates that some form of traffic management or regulation mechanism is present or applied to a given route, intersection, or transportation element.
  • B. hasBorderFacilityType
    Indicates that a border facility possesses or is classified by a specific type or category of border-related infrastructure or service.
  • C. hasTrafficControlCenter
    Indicates that an entity possesses or is served by a traffic control center responsible for monitoring and managing traffic operations.
  • D. hasTrafficRegime
    Indicates that a specified traffic control or regulatory system applies to a given road, area, or transport context.
  • E. hasBorderCrossingFunction
    Indicates that an entity serves as a location or facility where people, goods, or vehicles can legally cross a border between jurisdictions.
  • 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_69e77e89d5848190b54352cdb74f6029 completed April 21, 2026, 1:41 p.m.
NER Named-entity recognition batch_69f65b14512c8190a40e70319dcc54cd completed May 2, 2026, 8:14 p.m.
PD Predicate disambiguation batch_69f659cc571c819097e51e531961d812 completed May 2, 2026, 8:08 p.m.
PDg Predicate description generation batch_69f65a9cb0bc8190bf8a9b319900bad5 completed May 2, 2026, 8:12 p.m.
Created at: April 22, 2026, 9:01 a.m.