Triple
T35972187
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dibër region |
E1040315
|
entity |
| Predicate | crossesHistoricalRegion |
P149357
|
FINISHED |
| Object | Maqellarë–Debar area |
—
|
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: Maqellarë–Debar area | Statement: [Dibër region, crossesHistoricalRegion, Maqellarë–Debar area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crossesHistoricalRegion Context triple: [Dibër region, crossesHistoricalRegion, Maqellarë–Debar area]
-
A.
historicalRegionCrossed
chosen
Indicates that one entity passes through or traverses the territory of a historically defined region.
-
B.
historicalRegion
Indicates that an entity is or was a geographically defined area recognized for its significance during a particular historical period.
-
C.
crossesRegion
Indicates that an entity moves through or passes across the spatial extent of a specified region.
-
D.
historicalStatusOfRegion
Indicates the historical political or administrative status that a region held during a specific past period.
-
E.
historicalRegionCorrespondsTo
Indicates that a historical region matches or aligns with a specific region, territory, or administrative unit in terms of location, extent, or identity.
- 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_69f76e27758c81909b711cf38a130aaf |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fcda3699948190adb57625bae08091 |
completed | May 7, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fd16d08190b0aca6e19a632e99 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:07 p.m.