Triple

T3262430
Position Surface form Disambiguated ID Type / Status
Subject Amtrak Maple Leaf E68441 entity
Predicate borderServiceCategory P46943 FINISHED
Object preclearance not available on train 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: preclearance not available on train | Statement: [Amtrak Maple Leaf, borderServiceCategory, preclearance not available on train]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: borderServiceCategory
Context triple: [Amtrak Maple Leaf, borderServiceCategory, preclearance not available on train]
  • A. borderSectionName
    Indicates the specific named segment or portion of a border that is associated with or applies to an entity.
  • B. borderContext
    Indicates that one entity serves as a contextual or reference boundary that defines, constrains, or frames the scope or limits of another entity or interaction.
  • C. borderDefinedBy
    Indicates that the boundary or limit of one entity is determined, shaped, or delineated by another entity.
  • D. borderRegion
    Indicates a region that lies along or near the boundary separating two distinct geographic or political areas.
  • E. borderCharacteristic
    Indicates that one entity specifies a property, feature, or quality of the border or boundary of another entity.
  • 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_69ad8590444081909e8107a8aeef3a23 completed March 8, 2026, 2:20 p.m.
NER Named-entity recognition batch_69adafa908e881908cbb2ad137819ffb completed March 8, 2026, 5:19 p.m.
PD Predicate disambiguation batch_69ada41d7eac8190ada4bf5f793d5c49 completed March 8, 2026, 4:30 p.m.
PDg Predicate description generation batch_69ada525bb2c8190b773efe6d696b6ab completed March 8, 2026, 4:34 p.m.
Created at: March 8, 2026, 3:09 p.m.