Triple
T21535315
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swiss customs territory |
E531334
|
entity |
| Predicate | borderControlsApplyTo |
P121973
|
FINISHED |
| Object | imports |
—
|
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: imports | Statement: [Swiss customs territory, borderControlsApplyTo, imports]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderControlsApplyTo Context triple: [Swiss customs territory, borderControlsApplyTo, imports]
-
A.
borderControls
Indicates that one entity enforces or administers border control measures over another entity or at a specific boundary.
-
B.
borderControlSide
Indicates that one entity is positioned on or associated with a particular side or segment of a border control area or checkpoint.
-
C.
borderControlMeasure
chosen
Indicates a policy or action implemented to regulate, monitor, or restrict the movement of people or goods across a border.
-
D.
borderControlCoordinatedWith
Indicates that one entity coordinated its border control activities or policies with another entity.
-
E.
borderOpening
Indicates that a border between two regions is being opened or made accessible for crossing or interaction.
- 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_69e0c45e5b8881908ac18fc2f493b114 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ee9d0ce8d08190b3233d7117a9b1ca |
completed | April 26, 2026, 11:17 p.m. |
| PD | Predicate disambiguation | batch_69e6320766308190ba5dca2f7c826aa4 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:27 p.m.