Triple
T19282802
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Karaburun-Sazan Marine National Park |
E482231
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | protected area of Albania |
C42219
|
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: protected area of Albania Context triple: [Karaburun-Sazan Marine National Park, instanceOf, protected area of Albania]
-
A.
county of Albania
A county of Albania is a primary administrative division of the country that encompasses multiple municipalities and serves as a regional unit for governance, planning, and public services.
-
B.
core region of Montenegro
The core region of Montenegro is the central, historically and administratively significant area of the country that encompasses key political, cultural, and economic centers.
-
C.
protected area of Poland
A protected area of Poland is a designated geographic region safeguarded by law to conserve its natural landscapes, biodiversity, and cultural heritage, often restricting certain human activities to ensure long-term environmental protection.
-
D.
Arbëreshë settlement
An Arbëreshë settlement is a community established by the Italo-Albanian (Arbëreshë) people, characterized by the preservation of their distinct Albanian language, Byzantine religious rites, and cultural traditions within Italy.
-
E.
autonomous region of Greece
An autonomous region of Greece is a geographically defined area within the Greek state that possesses a special legal status granting it a degree of self-governance distinct from the country’s standard administrative divisions.
- F. None of above. chosen
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_69d8e8cf61b0819096fe3e4107827c4e |
completed | April 10, 2026, 12:10 p.m. |
Created at: April 10, 2026, 1:30 p.m.