Triple

T27336520
Position Surface form Disambiguated ID Type / Status
Subject Borssele E689965 entity
Predicate inSchengenArea P11465 FINISHED
Object true 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: true | Statement: [Borssele, inSchengenArea, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: inSchengenArea
Context triple: [Borssele, inSchengenArea, true]
  • A. hasSchengenArea chosen
    Indicates that a place, country, or region is part of, or included within, the Schengen Area for border-free movement.
  • B. isSchengenExternalBorder
    Indicates that a given border segment functions as an external boundary between the Schengen Area and non-Schengen territories.
  • C. haveSimilarStatusInSchengen
    Indicates that two entities share a comparable legal or administrative status within the Schengen area.
  • D. граничитСтранаЕС
    Indicates that a country shares a land or maritime border with a member state of the European Union.
  • E. supportsSchengenFlights
    Indicates that an entity enables or accommodates flights operating within the Schengen Area.
  • 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_69ef355e5b388190a8fc1eba9b4a6656 completed April 27, 2026, 10:07 a.m.
NER Named-entity recognition batch_69f62acff3148190b836044eaadb1f9b completed May 2, 2026, 4:48 p.m.
PD Predicate disambiguation batch_69f620e4b1c88190a17940251abc68fd completed May 2, 2026, 4:05 p.m.
Created at: April 27, 2026, 11:40 a.m.