Triple
T18971577
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Greater Region of Saar-Lor-Lux |
E464182
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | cross-border cooperation area |
C7343
|
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: cross-border cooperation area Context triple: [Greater Region of Saar-Lor-Lux, instanceOf, cross-border cooperation area]
-
A.
cross-border area
chosen
A cross-border area is a geographic region that spans across the boundaries of two or more countries, where social, economic, environmental, and political interactions occur and are often managed through cooperative arrangements.
-
B.
cross‑border operation
A cross-border operation is an organized activity or transaction conducted across the legal, regulatory, or geographic boundaries of two or more countries.
-
C.
cross-border institution
A cross-border institution is an organization or entity that operates across national boundaries, coordinating policies, activities, or services between multiple countries or jurisdictions.
-
D.
international agreement implementation area
The international agreement implementation area is a defined domain—such as a sector, region, or policy field—within which the provisions of an international agreement are applied, monitored, and enforced.
-
E.
transboundary region
A transboundary region is a geographically contiguous area that spans across the borders of two or more political or administrative jurisdictions, sharing interconnected environmental, economic, social, or cultural systems.
- 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_69d8dd008af48190a97ff1c6488edf1b |
completed | April 10, 2026, 11:20 a.m. |
Created at: April 10, 2026, noon