Triple
T29810369
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bratislava–Rajka area |
E756943
|
entity |
| Predicate | withinSchengenArea |
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: [Bratislava–Rajka area, withinSchengenArea, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: withinSchengenArea Context triple: [Bratislava–Rajka area, withinSchengenArea, 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.
supportsSchengenFlights
Indicates that an entity enables or accommodates flights operating within the Schengen Area.
-
E.
граничитСтранаЕС
Indicates that a country shares a land or maritime border with a member state of the European Union.
- 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_69f2245584848190ad4cab1f07752ccb |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6752de184819086c6665f614f71a6 |
completed | May 2, 2026, 10:05 p.m. |
| PD | Predicate disambiguation | batch_69f66ac1a4fc81909740d2e52fbe6970 |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 29, 2026, 5:23 p.m.