Triple
T24565461
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Żory |
E607773
|
entity |
| Predicate | hasCulturalRegionIdentity |
P110723
|
FINISHED |
| Object | Silesian |
—
|
NE NERFINISHED |
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: Silesian | Statement: [Żory, hasCulturalRegionIdentity, Silesian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCulturalRegionIdentity Context triple: [Żory, hasCulturalRegionIdentity, Silesian]
-
A.
hasStrongCulturalIdentity
Indicates that an entity possesses a well-defined, deeply rooted, and strongly maintained sense of belonging to a particular culture or cultural tradition.
-
B.
culturalIdentifier
Indicates that one entity serves as a marker, label, or attribute that identifies or characterizes the cultural affiliation, background, or context of another entity.
-
C.
culturalIdentityTiedTo
Indicates that an entity’s cultural identity is closely connected or strongly associated with another specified entity or context.
-
D.
isCulturalArea
chosen
Indicates that a given area is recognized or designated as a cultural region, characterized by shared cultural traits, practices, or heritage.
-
E.
namedForCulturalRegion
Indicates that something is given a name derived from or honoring a specific cultural region.
- 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_69e2c4cc35a48190990b7571bc086df8 |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2a92082a881908896dcdda85559b9 |
completed | April 30, 2026, 12:58 a.m. |
| PD | Predicate disambiguation | batch_69f2a6b99e7c8190ba7e2dc8729a314a |
completed | April 30, 2026, 12:47 a.m. |
Created at: April 18, 2026, 2:28 a.m.