Triple
T33327052
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Strážske |
E853292
|
entity |
| Predicate | borderRegulation |
P3948
|
FINISHED |
| Object | Schengen Area rules |
—
|
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: Schengen Area rules | Statement: [Strážske, borderRegulation, Schengen Area rules]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderRegulation Context triple: [Strážske, borderRegulation, Schengen Area rules]
-
A.
borderRegime
chosen
Indicates the type, rules, or control system governing how movement or interaction is managed across a border between entities.
-
B.
borderTradePointWith
Indicates a location or facility where trade or commercial exchange occurs between two bordering regions or countries.
-
C.
borderTradeStatus
Indicates the current condition or level of activity of trade occurring across a shared border between two regions or countries.
-
D.
borderPostIs
Indicates that one entity functions as a border post associated with or located at another entity.
-
E.
borderPostType
Indicates the specific kind or classification of a border post associated with a boundary or crossing point.
- 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_69f349685f088190b8fda44083a018a9 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff38b960808190a8263348f1e5c0e4 |
completed | May 9, 2026, 1:38 p.m. |
| PD | Predicate disambiguation | batch_69ff37d97d9c8190849b2bac14f9af1d |
completed | May 9, 2026, 1:34 p.m. |
Created at: May 1, 2026, 1:33 a.m.