Triple
T28815244
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Common Travel Area |
E727623
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | free-movement zone |
C1089
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: free-movement zone Context triple: [Common Travel Area, instanceOf, free-movement zone]
-
A.
free trade zone
A free trade zone is a designated geographic area within a country where goods can be imported, stored, processed, and re-exported with reduced or eliminated customs duties and regulatory barriers to promote trade and investment.
-
B.
tariff zone
A tariff zone is a defined geographic area within which specific pricing rules, rates, or charges apply for goods, services, or transportation.
-
C.
free trade area agreement
A free trade area agreement is a treaty between two or more countries that eliminates tariffs and other trade barriers on most goods and services traded among them while allowing each country to maintain its own external trade policies toward non-members.
-
D.
fare-free public transport zone
A fare-free public transport zone is an area within a transit network where passengers can use public transportation services without paying a fare, typically to encourage ridership, reduce congestion, and support environmental or economic goals.
-
E.
international-free internal border
chosen
An international-free internal border is a boundary between two or more countries within which people, goods, and services can move without routine border checks, controls, or significant legal restrictions.
- F. None of above.
Provenance (1 batch)
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_69f0319d09088190bbf14cdf1987792a |
completed | April 28, 2026, 4:03 a.m. |
Created at: April 28, 2026, 6:32 a.m.