Triple
T14812622
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pałuki |
E348221
|
entity |
| Predicate | hasCulturalRegionCode |
P1968
|
FINISHED |
| Object | ethnographic region of Poland |
—
|
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: ethnographic region of Poland | Statement: [Pałuki, hasCulturalRegionCode, ethnographic region of Poland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCulturalRegionCode Context triple: [Pałuki, hasCulturalRegionCode, ethnographic region of Poland]
-
A.
hasRegionCode
Indicates that an entity is associated with a specific regional identifier or code.
-
B.
isCulturalArea
Indicates that a given area is recognized or designated as a cultural region, characterized by shared cultural traits, practices, or heritage.
-
C.
culturalRegion
chosen
Indicates that an entity is located in, associated with, or belongs to a specific cultural region or cultural area.
-
D.
culturalAreaIncludes
Indicates that a broader cultural area encompasses or contains a smaller cultural region or entity within its scope.
-
E.
hasCanonicalTerritory
Indicates that an entity possesses an officially recognized or standard territorial area associated with it.
- 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_69d822eb8f588190bf53445e730a934f |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69decf374f288190aa918b1b6b507420 |
completed | April 14, 2026, 11:35 p.m. |
| PD | Predicate disambiguation | batch_69de8c0ef8a4819092d84478b1f56db1 |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:48 a.m.